Jira (PUP-5208) owner uid --> integer 4294967294 too big to convert to `int'
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-5208 owner uid --> integer 4294967294 too big to convert to `int' Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6608) variable scoping change in Puppet 4.6.0
Title: Message Title Phong Ly commented on PUP-6608 Re: variable scoping change in Puppet 4.6.0 Bug fixed, tested with puppet-agent at SHA 092d3dc7 Tested with --strict_variables root@nkwd9ocoq7a3lh8:~# puppet apply --strict_variables test_with-strict_variables.pp Warning: Could not retrieve fact ipaddress Notice: Compiled catalog for nkwd9ocoq7a3lh8.delivery.puppetlabs.net in environment production in 0.08 seconds Notice: goodbye Notice: /Stage[main]/Main/Notify[goodbye]/message: defined 'message' as 'goodbye' Notice: Applied catalog in 0.03 seconds root@nkwd9ocoq7a3lh8:~# root@nkwd9ocoq7a3lh8:~# cat test_with-strict_variables.pp
Jira (PUP-6623) Add function for unwrapping sensitive data
Title: Message Title Adrien Thebo created an issue Puppet / PUP-6623 Add function for unwrapping sensitive data Issue Type: New Feature Assignee: Unassigned Created: 2016/08/16 4:02 PM Priority: Normal Reporter: Adrien Thebo When users are handling sensitive data they may need to look at values stored within a sensitive type. For instance, if a password is marked as sensitive it may need to be interpolated into a string, and Sensitive objects have to be unwrapped before they can be interpolated. Puppet needs a function to briefly expose this data for such use cases. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2888) Add flag for turning off historical catalogs (JSONB related storage) in PuppetDB
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-2888 Add flag for turning off historical catalogs (JSONB related storage) in PuppetDB Change By: Nick Walker Summary: Add flag for turning off historical catalogs ( JSONB related storage ) in PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2908) Resolve conflict between i18n and structured-logging
Title: Message Title Larissa Lane updated an issue PuppetDB / PDB-2908 Resolve conflict between i18n and structured-logging Change By: Larissa Lane Labels: i18n Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6608) variable scoping change in Puppet 4.6.0
Title: Message Title Phong Ly updated an issue Puppet / PUP-6608 variable scoping change in Puppet 4.6.0 Change By: Phong Ly QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6608) variable scoping change in Puppet 4.6.0
Title: Message Title Phong Ly assigned an issue to Phong Ly Puppet / PUP-6608 variable scoping change in Puppet 4.6.0 Change By: Phong Ly Assignee: qa Phong Ly Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6502) puppet calls dscl pathologically often
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6502 puppet calls dscl pathologically often Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1413) External facts do not override custom Ruby facts that have confines or a non-default weight
Title: Message Title John Duarte assigned an issue to qa Facter / FACT-1413 External facts do not override custom Ruby facts that have confines or a non-default weight Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6608) variable scoping change in Puppet 4.6.0
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6608 variable scoping change in Puppet 4.6.0 Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6597) puppet generate types outputs bogus paths of generated files
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6597 puppet generate types outputs bogus paths of generated files Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5623) Callable type, function, and block definitions, can be declared with return type
Title: Message Title John Duarte commented on PUP-5623 Re: Callable type, function, and block definitions, can be declared with return type Henrik Lindberg, do we need any release notes or are they covered by the higher level feature docs? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: John Duarte Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-5832
4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Change By:
Eric Thompson
We currently have no good way of handling sensitive data in a puppet manifest.In PUP-5831 we are adding a binary type. Ticket PUP-3600 is about making that Binary type work as content in an unmodified 3.x PSON/JSON encoded catalog for the File content attribute, but only there. That is not enough for Binary, and certainly no enough for Sensitive data.While other attributes could possibly also be handled as special cases,there is no general handling of binary until we have better serialization. (TBD Ref to ticket). While Binary works for some attributes, it makes it hard to support as the receiving end must know that it may get binary data, and what that binary data represents. Say that it should be a secret Integer - how does the receiver know this and not mistake for say a GIF?To support this, we add a new type; {{Sensitive\[T, chipher]}}, a subtype of {{Binary}} where {{T}} represents the unencrypted value type, and {{chiper}} a chipher reference as in OpenSSL::Chipher. A runtime object maintains both the encrypted and unencrypted value, or just the encrypted value. A {{Sensitive}} value may have to be able to present itself in a surrogate form i certain situations, such a surrogate value must be of the actual data type or usage may break.It is uncertain if the surrogate is of value or if this is a presentation issue as each presentation technology may be happy with just a sequence of asterisks for any data type, a very narrow type (like an Enum would also not be able to have a surrogate if the surrogate is one of the acceptable values. For those reasons a surrogate value should not be included in the design. The Boolean 'value_available' attribute is used to denote if the value attribute is available. This boolean is needed as the value {{T}} may accept {{Undef}}.Thus a sensitive object can be described by he struct type:{code:puppet}Struct[{ value => T, chipher => String, data => Hash[String, Binary], value_available => Boolean }]{code}When creating an instance of {{Sensitive}}, the data may come from a data source where the value is already encrypted. Data sources that supports this, should return an instance of Sensitive instead of the String representation. The data source will have some way of representing the Cipher as well as the encrypted value. When a {{Sensitive}} is created from unencrypted source enough information must be given to enable encryption. The sensitive data can hold multiple encrypted values, one for each recipient. The typical use cases is to allow the master to see the value for the purpose of deriving new values, and for a node, or nodes..The most common case would be to encrypt for a node - the clear data is only readable by the node, but other scenarios may apply (a certificate shared by a group etc.). Information available only to the master, then made available to a node etc. The method that creates a sensitive must therefore be able to handle these various options.In this proposal, the keyname is assumed to uniquely identify a name, and that a node's fqdn is such a suitable key.{code:puppet}Sensitive.new(String $cipher,
Jira (PUP-6619) PUP ticket for adding tests for PA-466
Title: Message Title Ethan Brown commented on PUP-6619 Re: PUP ticket for adding tests for PA-466 Merged to stable in https://github.com/puppetlabs/puppet/commit/756ce4f8edab58261b73a3c14d9143b5eadbc6e3 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2985 Fix excessive CPU usage by clj-i18n Issue Type: Bug Assignee: Unassigned Created: 2016/08/16 2:41 PM Priority: Normal Reporter: Ryan Senior Doing some rough profiling of command enqueuing found 40% of CPU being eaten by clj-i18n. The issue appears to be repeated reading/parsing of the locale CLJ file. We should try putting that behind a delay and derefing it each time to ensure we don't reread that file for each trs/tru invocation. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2984) (maint) Have s3 resolve symlinks for apt repo sync
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2984 (maint) Have s3 resolve symlinks for apt repo sync Issue Type: Bug Assignee: Unassigned Created: 2016/08/16 2:36 PM Priority: Normal Reporter: gepetto-bot This commit updates the s3 command used to sync out apt repos to s3. This change is meant to help enable the switchover from reprepro to aptly for apt repo creation. In order to maintain the current expected repo format with aptly, we are forced to create symlinks. However, since s3 does not support symlinks, we need to ensure they are resolved before we attempt to send those files to s3. The addition of this flag handles that. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-2983) Ensure PDB + Stockpile is HUPable
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2983 Ensure PDB + Stockpile is HUPable Issue Type: Task Assignee: Unassigned Created: 2016/08/16 2:33 PM Priority: Normal Reporter: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-2982) Create shorter command names for the stockpile metadata
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2982 Create shorter command names for the stockpile metadata Issue Type: New Feature Assignee: Unassigned Created: 2016/08/16 2:31 PM Priority: Normal Reporter: Ryan Senior Currently the command name is used in the Stockpile metadata string. There's nothing technical wrong with this, but it's long and it's less user friendly as there's spaces. Now we have "replace catalog" in the middle of a stockpile command name, instead we should just output "rc" or "cat" or something similar Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2981) Output most useful metrics via the status endpoint like Puppetsever does
Title: Message Title
Nick Walker updated an issue
PuppetDB / PDB-2981
Output most useful metrics via the status endpoint like Puppetsever does
Change By:
Nick Walker
PuppetDB has a wealth of metrics but it's often difficult to determine which ones Puppet thinks are important. As a user of PuppetDB, I'd like PuppetDB to curate a set of metrics that are considered to be important metrics to use for tracking and troubleshooting performance. Puppetserver already does something like this and outputs them via the status endpoint of their API. It'd be great if PuppetDB could do the same. Example output from puppetserver: {code}[root@master201611-centos tmp]# cat /opt/puppetlabs/pe_metric_curl_cron_jobs/puppet_server/localhost-08_12_16_21\:02.json{"pe-jruby-metrics": {"detail_level": "debug","service_status_version": 1,"service_version": "2016.1.1014","state": "running","status": {"experimental": {"jruby-pool-lock-status": {"current-state": ":not-in-use","last-change-time": "2016-08-12T20:46:18.114Z"},"metrics": {"average-borrow-time": 1226,"average-free-jrubies": 0.9976127247536,"average-lock-held-time": 0,"average-lock-wait-time": 0,"average-requested-jrubies": 0.0,"average-wait-time": 0,"borrow-count": 15,"borrow-retry-count": 0,"borrow-timeout-count": 0,"borrowed-instances": [],"num-free-jrubies": 1,"num-jrubies": 1,"num-pool-locks": 0,"requested-count": 15,"requested-instances": [],"return-count": 15}}}},"pe-master": {"detail_level": "debug","service_status_version": 1,"service_version": "2016.1.1014","state": "running","status": {"experimental": {"http-metrics": [{"aggregate": 18420,"count": 15,"mean": 1228,"route-id": "total"},{"aggregate": 6767,"count": 1,"mean": 6767,"route-id": "puppet-v3-node-/*/"},{"aggregate": 4788,"count": 2,"mean": 2394,"route-id": "puppet-v3-environment_classes-/*/"},{"aggregate": 1407,"count": 3,"mean": 469,"route-id": "puppet-v3-file_metadatas-/*/"},{"aggregate": 1330,"count": 1,"mean": 1330,"route-id": "puppet-v3-catalog-/*/"},{
Jira (PDB-2981) Output most useful metrics via the status endpoint like Puppetsever does
Title: Message Title Nick Walker created an issue PuppetDB / PDB-2981 Output most useful metrics via the status endpoint like Puppetsever does Issue Type: New Feature Assignee: Unassigned Created: 2016/08/16 2:29 PM Labels: tcse Priority: Normal Reporter: Nick Walker PuppetDB has a wealth of metrics but it's often difficult to determine which ones Puppet thinks are important. As a user of PuppetDB, I'd like PuppetDB to curate a set of metrics that are considered to be important metrics to use for tracking and troubleshooting performance. Puppetserver already does something like this and outputs them via the status endpoint of their API. It'd be great if PuppetDB could do the same. Add Comment
Jira (PUP-6619) PUP ticket for adding tests for PA-466
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-6619 PUP ticket for adding tests for PA-466 Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6619) PUP ticket for adding tests for PA-466
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6619 PUP ticket for adding tests for PA-466 Change By: Ethan Brown Sprint: Windows 2016-08-24 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2953) Implement certname "bash in place"
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2953 Implement certname "bash in place" Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6619) PUP ticket for adding tests for PA-466
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6619 PUP ticket for adding tests for PA-466 Change By: Ethan Brown Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2980) (maint) don't dump test log on failure
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2980 (maint) don't dump test log on failure Issue Type: Bug Assignee: Unassigned Created: 2016/08/16 2:10 PM Priority: Normal Reporter: gepetto-bot Dumping the log on failure will produce a log file that is too big for travis to handle, causing the job to get aborted. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6622) Puppet function_loading benchmark performance degredation
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6622 Puppet function_loading benchmark performance degredation Change By: Ethan Brown Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6622) Puppet function_loading benchmark performance degredation
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6622
Puppet function_loading benchmark performance degredation
Change By:
Ethan Brown
On Windows 2008R2 / Ruby 2.1, commit https://github.com/puppetlabs/puppet/commit/01db61e24178a3baebbeaa1c58250fcbf447d8bc introduced a 10x performance degredation for the {{benchmark:function_loading}} micro-benchmark in the Puppet suite. I used git bisect to identify that particular commit.h3. For {{2211c64}} (parent of {{01db61e}}){code}C:\source\puppet [(2211c64...) +68 ~0 -0 !]> bundle exec rake benchmark:function_loadingDocument generation not available without yard. cannot load such file -- yardmkdir -p C:/Users/ADMINI~1/AppData/Local/Temp/function_loading20160816-3900-13bswjgDL is deprecated, please use Fiddle user system totalrealRun 1 10.296000 2.125000 12.421000 ( 13.608853)Run 26.766000 1.031000 7.797000 ( 8.749664)Run 38.078000 0.797000 8.875000 ( 9.692987)Run 48.578000 0.891000 9.469000 ( 10.468348)Run 59.094000 0.844000 9.938000 ( 10.937080)Run 69.984000 0.844000 10.828000 ( 12.093286)Run 7 10.61 0.844000 11.454000 ( 12.629397)Run 8 12.109000 0.843000 12.952000 ( 13.953529)Run 9 12.25 1.032000 13.282000 ( 14.311859)Run 10 13.438000 0.828000 14.266000 ( 15.218068)> total: 101.203000 10.079000 111.282000 (121.663071)> avg: 10.120300 1.007900 11.128200 ( 12.166307){code}h3. For {{01db61e}}{code}C:\source\puppet [(01db61e...) +68 ~0 -0 !]> bundle exec rake benchmark:function_loadingDocument generation not available without yard. cannot load such file -- yardmkdir -p C:/Users/ADMINI~1/AppData/Local/Temp/function_loading20160816-49440-1miin4uDL is deprecated, please use Fiddle user system totalrealRun 1 114.015000 14.797000 128.812000 (142.752140)Run 2 156.344000 14.547000 170.891000 (184.167353)Run 3 201.969000 13.188000 215.157000 (228.894914)Run 4 245.016000 12.828000 257.844000 (271.543842)Run 5 288.734000 13.312000 302.046000 (315.255168){code}NOTE: The above was terminated prematurely given the obvious trend of a further decrease of performance on each run.h3. Current stable HEAD ({{13d208b2e935151c6b8cf77e8bf4ad1b45fc72c5}}) as of 8/16/2016Some corrective efforts appear to have already been taken to address this performance problem (and it's compounding effect), but the current performance of latest code is still 3x slower than it was on versions of Puppet prior to {{4.6.0}}.{code}C:\source\puppet [stable...origin/stable +68 ~0 -0 !]> bundle exec rake benchmark:function_loadingDocument generation not available without yard. cannot load such file -- yardmkdir -p C:/Users/ADMINI~1/AppData/Local/Temp/function_loading20160816-10824-x58pt6DL is deprecated, please use Fiddle user system totalrealRun 1 29.266000 5.266000 34.532000 ( 35.654881)Run 2 24.453000 3.969000 28.422000 ( 29.694252)Run 3 25.563000 3.89 29.453000 ( 30.420901)Run 4 26.453000 3.797000 30.25 ( 31.485412)Run 5 27.219000 3.563000 30.782000 ( 31.846841)Run 6 30.39 3.328000 33.718000 ( 34.311228)Run 7
Jira (PUP-6622) Puppet function_loading benchmark performance degredation
Title: Message Title Ethan Brown created an issue Puppet / PUP-6622 Puppet function_loading benchmark performance degredation Issue Type: Bug Affects Versions: PUP 4.6.0 Assignee: Unassigned Created: 2016/08/16 1:44 PM Fix Versions: PUP 4.6.1 Priority: Normal Reporter: Ethan Brown On Windows 2008R2 / Ruby 2.1, commit https://github.com/puppetlabs/puppet/commit/01db61e24178a3baebbeaa1c58250fcbf447d8bc introduced a 10x performance degredation for the benchmark:function_loading micro-benchmark in the Puppet suite. I used git bisect to identify that particular commit. For 2211c64 (parent of 01db61e) C:\source\puppet [(2211c64...) +68 ~0 -0 !]> bundle exec rake benchmark:function_loading
Jira (PUP-4889) Direct Puppet Initiative
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-4889 Direct Puppet Initiative Change By: Karen Van der Veer Scrum Team/s: Client Platform,Language ,Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Karen Van der Veer Scrum Team/s: Client Platform,Language, Puppet Server, PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3640) Green: Puppet 5.0 Changes
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-3640 Green: Puppet 5.0 Changes Change By: Karen Van der Veer Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6586) User resource always reports password changed when account disabled
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-6586 User resource always reports password changed when account disabled Change By: Rob Reynolds Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6621) Puppet Agent 1.6.0 causing 'Could not evaluate' errors on Cisco Module
Title: Message Title Branan Riley moved an issue Puppet / PUP-6621 Puppet Agent 1.6.0 causing 'Could not evaluate' errors on Cisco Module Change By: Branan Riley Fix Version/s: puppet-agent 1.6.1 Fix Version/s: PUP 4.6.1 Affects Version/s: puppet-agent 1.6.0 Affects Version/s: PUP 4.6.0 Workflow: Release Engineering Scrum Teams Workflow Key: PA PUP - 473 6621 Project: Puppet Agent Add Comment
Jira (PUP-6621) Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it
Title: Message Title Branan Riley updated an issue Puppet / PUP-6621 Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it Change By: Branan Riley Summary: Corrective Change in Puppet Agent 1 4 .6.0 causing 'Could not evaluate' incorrectly errors on Cisco Module when custom types are incompatible with it Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6588) Allow context path in http_proxy
Title: Message Title Jainish Shah commented on PUP-6588 Re: Allow context path in http_proxy I have created PR : https://github.com/puppetlabs/puppet/pull/5190 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6620) Ensure test setup doesn't mask test failure of PMT to connect to Forge
Title: Message Title Moses Mendoza commented on PUP-6620 Re: Ensure test setup doesn't mask test failure of PMT to connect to Forge Yes indeed - moved. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6620) Ensure test setup doesn't mask test failure of PMT to connect to Forge
Title: Message Title Moses Mendoza moved an issue Puppet / PUP-6620 Ensure test setup doesn't mask test failure of PMT to connect to Forge Change By: Moses Mendoza Workflow: Release Engineering Scrum Teams Workflow Key: PA PUP - 472 6620 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6619) PUP ticket for adding tests for PA-466
Title: Message Title Moses Mendoza created an issue Puppet / PUP-6619 PUP ticket for adding tests for PA-466 Issue Type: Task Assignee: Unassigned Created: 2016/08/16 11:17 AM Priority: Normal Reporter: Moses Mendoza This ticket is track the addition of tests to prevent a recurrence of PA-466. See that linked ticket for additional detail. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2957) Fix PuppetDB CLI on Windows with Tokens
Title: Message Title John Duarte commented on PDB-2957 Re: Fix PuppetDB CLI on Windows with Tokens Using pe-client-tools at SHA 3d059d7, both puppet-db and puppet-query tools have been verified to sucessfully use a puppet-access token to authenticate to the PDB service-url. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2957) Fix PuppetDB CLI on Windows with Tokens
Title: Message Title Susan McNerney commented on PDB-2957 Re: Fix PuppetDB CLI on Windows with Tokens Issue came back, but after further work tests are now passing. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1487) Facter smoke tests fail on cisco-wrlinux7
Title: Message Title John Duarte updated an issue Facter / FACT-1487 Facter smoke tests fail on cisco-wrlinux7 Change By: John Duarte Labels: transient Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2952) spec tests fail on ruby 2.2.2
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2952 spec tests fail on ruby 2.2.2 Change By: Wyatt Alt Fix Version/s: PDB 4.2.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1487) Facter smoke tests fail on cisco-wrlinux7
Title: Message Title John Duarte commented on FACT-1487 Re: Facter smoke tests fail on cisco-wrlinux7 This cell fails in the same way when matrix reloaded with Jenkins Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1487) Facter smoke tests fail on cisco-wrlinux7
Title: Message Title John Duarte created an issue Facter / FACT-1487 Facter smoke tests fail on cisco-wrlinux7 Issue Type: CI Blocker Assignee: Unassigned Created: 2016/08/16 8:20 AM Priority: Normal Reporter: John Duarte Facter#stable is failing to build on cisco-wlinux-7. It is failing during the smoke test section of the build process. Jenkins CI Failure Error snippet 00:59:26 2/2 Test #2: facter smoke .***Failed 20.13 sec 00:59:26 00:59:26 50% tests passed, 1 tests failed out of 2 00:59:26
Jira (PUP-5871) Add Timestamp and Timespan to Puppet type system
Title: Message Title Thomas Hallgren commented on PUP-5871 Re: Add Timestamp and Timespan to Puppet type system Regarding format characters. I'd like to avoid using the ISO-8601 way of describing formats since there's no implementation backing it. Instead, I'd like to use the commonly used formats for strftime (Ruby, C++). %a – Abbreviated weekday (Sun.) %A – Full weekday (Sunday) %b – Abbreviated month (Jan.) %B – Full month (January) %d – Day of Month [01,31] %e – Day of Month [1,31] %h – Same as %b %H – 24 clock hour [00,23] %I – 12 clock hour [01,12] %j – Day of year [1,366] %m – Month [01,12] %M – Minute [00,59] %n – New Line %p – AM/PM in locale representation %r – Time with AM/PM, same as %I:%M:%S %p %R – Same as %H:%M %S – Second [00,61] * %L - Millisecond of the second %N - Fractional seconds digits. Default is nanoseconds but it can also be written as %3N (milliseconds), %6N (microseconds) %9N (nanoseconds).
Jira (PUP-5871) Add Timestamp and Timespan to Puppet type system
Title: Message Title Thomas Hallgren commented on PUP-5871 Re: Add Timestamp and Timespan to Puppet type system I think the timespan format must be simplified to only reflect days, hours, minutes, seconds, milliseconds, and nanoseconds. Reason being that if we mix in year, month, and day in month, it gets complicated since leap years will make their values differ depending on when the timespan is applied. If the largest digit signifies days, we don't have that problem. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6618) type: user, fails in macOS with UTF-8 related errors
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6618 type: user, fails in macOS with UTF-8 related errors Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6618) type: user, fails in macOS with UTF-8 related errors
Title: Message Title Kylo Ginsberg commented on PUP-6618 Re: type: user, fails in macOS with UTF-8 related errors Per comments above, I'm resolving this as a dup of PUP-6159 . Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6618) type: user, fails in macOS with UTF-8 related errors
Title: Message Title Henry Dobson updated an issue Puppet / PUP-6618 type: user, fails in macOS with UTF-8 related errors 4.6.0 resolved Completely missed ticket PUP-6159 in my searches to resolve this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6618) type: user, fails in macOS with UTF-8 related errors
Title: Message Title Henry Dobson updated an issue Puppet / PUP-6618 type: user, fails in macOS with UTF-8 related errors Change By: Henry Dobson Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6618) type: user, fails in macOS with UTF-8 related errors
Title: Message Title Henry Dobson assigned an issue to Kylo Ginsberg Puppet / PUP-6618 type: user, fails in macOS with UTF-8 related errors Change By: Henry Dobson Assignee: Kylo Ginsberg Affects Version/s: PUP 4.5.3 Component/s: Types and Providers Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6618) type: user, fails in macOS with UTF-8 related errors
Title: Message Title Henry Dobson created an issue Puppet / PUP-6618 type: user, fails in macOS with UTF-8 related errors Issue Type: Bug Assignee: Unassigned Created: 2016/08/16 4:01 AM Environment: puppetserver version: 2.4.0 puppetserver ruby version: ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-linux] puppetserver gems: CFPropertyList (2.3.2) digest (0.0.1) jar-dependencies (0.1.13) jdbc-sqlite3 (3.8.11.2) jruby-openssl (0.9.7 java) json (1.8.0 java) rake (10.1.0) rdoc (4.1.2) puppet agent version: 4.5.3 puppet agent OS: macOS 10.11.6 puppet agent ruby version: ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15] puppet agent gems: bigdecimal (1.2.8) CFPropertyList (2.3.2) did_you_mean (1.0.0)
Jira (PUP-5871) Add Timestamp and Timespan to Puppet type system
Title: Message Title Thomas Hallgren commented on PUP-5871 Re: Add Timestamp and Timespan to Puppet type system I think the arithmetic for Timestamp should be limited so that multiplication, division, and addition is illegal. They all require a fixed starting point which in turn opens up a can of worms since you need to consider regional differences. And even if we do sort that out (or simply claim that it's the Epoch), what's the point in allowing it? I find no viable use-case. This means that the only possible arithmetic involving Timestamp is: Timestamp + Timespan = Timestamp Timestamp - Timespan = Timestamp Timestamp - Timestamp = Timespan Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Fabien Wernli created an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Issue Type: Bug Affects Versions: PUP 4.5.3 Assignee: Unassigned Created: 2016/08/16 1:55 AM Environment: master Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccsvli80 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux puppetserver --version puppetserver version: 2.4.0 puppetserver gem list Warning: The following options to parse-opts are unrecognized: :flag LOCAL GEMS *** collectd-dsl (0.3.6cc, 0.3.5) hiera-eyaml (2.1.0) hiera-eyaml-gpg (0.6) highline (1.6.21) jar-dependencies (0.1.13) jruby-openssl (0.9.7 java) json (1.8.0 java) mini_portile2 (2.1.0) rake (10.1.0) rdoc (4.1.2) ruby_gpg (0.3.2) trollop (2.1.2) uuidtools (2.1.5) agent Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccosvms0033 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Jira (PUP-6602) Acceptance: Add test for pcore loader precedence
Title: Message Title Thomas Hallgren commented on PUP-6602 Re: Acceptance: Add test for pcore loader precedence Merged to master at 50a20b2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6613) regression: explicit undef cannot be used in create_resources
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6613 regression: explicit undef cannot be used in create_resources Change By: Thomas Hallgren Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6574) Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6574 Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6574) Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator
Title: Message Title Thomas Hallgren commented on PUP-6574 Re: Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator Stable merged to master at 87b9358 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6574) Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator
Title: Message Title Thomas Hallgren commented on PUP-6574 Re: Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator Merged to stable at 13d208b Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
