Jira (PUP-4889) Direct Puppet Initiative
Title: Message Title Chris Price updated an issue Puppet / PUP-4889 Direct Puppet Initiative Change By: Chris Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6865) puppet 4.8.0 breaks code that uses strftime()
Title: Message Title Chris Price commented on PUP-6865 Re: puppet 4.8.0 breaks code that uses strftime() I am not aware of any dependency between Puppet and Puppet Server related to this issue. Matthaus Owens's explanation would make the most sense to me. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Chris Price commented on PUP-6474 Re: Incorporate gettext_setup gem into puppet Derp, I created SERVER-1600 to capture the server work, without reading closely enough to see that Branan Riley already had SERVER-1593. I don't want to mess with SERVER-1593 since it is already assigned to a team, so I'm just going to do the work for SERVER-1600 and link it to SERVER-1593 as a dupe. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6484) Productize 'lookup'
Title: Message Title Chris Price commented on PUP-6484 Re: Productize 'lookup' Thomas Hallgren thanks. PUP-6811 needs an owner, so if your team is able to write that test that would definitely help keep things moving along. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6484) Productize 'lookup'
Title: Message Title Chris Price commented on PUP-6484 Re: Productize 'lookup' Lindsey Smith I'm not sure if the "strings" code ever gets executed by the server. If it doesn't, then it's not an issue. If it does, then you are correct. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6484) Productize 'lookup'
Title: Message Title Chris Price commented on PUP-6484 Re: Productize 'lookup' Henrik Lindberg Thomas Hallgren we are working through the last few details about packaging gems in puppetserver. I've linked PA-621 and PUP-6811 as blockers for this ticket, because I think those need to happen before we can ship this stuff. Happy to discuss if you have any thoughts / comments. /cc Branan Riley Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3077) Integrate Ezbake service reload and logback/logrotate changes into PuppetDB
Title: Message Title Chris Price assigned an issue to Jeremy Barlow PuppetDB / PDB-3077 Integrate Ezbake service reload and logback/logrotate changes into PuppetDB Change By: Chris Price Assignee: Jeremy Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6537) unresolvable environment catalogs are compiled
Title: Message Title Chris Price updated an issue Puppet / PUP-6537 unresolvable environment catalogs are compiled Change By: Chris Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5678) Dependency File [/etc/sudoers] has failures: true
Title: Message Title Chris Price updated an issue Puppet / PUP-5678 Dependency File [/etc/sudoers] has failures: true Change By: Chris Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5679) Double entries in logfile
Title: Message Title Chris Price updated an issue Puppet / PUP-5679 Double entries in logfile Change By: Chris Price Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-524) determine strategy for something like eyaml for hocon
Title: Message Title Chris Price updated an issue Hiera / HI-524 determine strategy for something like eyaml for hocon Change By: Chris Price Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Chris Price Sub-team: emerald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3054) Externalize user facing strings in the tk-webserver-jetty9 repo
Title: Message Title Chris Price updated an issue PuppetDB / PDB-3054 Externalize user facing strings in the tk-webserver-jetty9 repo Change By: Chris Price Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3055) Externalize user facing strings in the trapperkeeper repo
Title: Message Title Chris Price updated an issue PuppetDB / PDB-3055 Externalize user facing strings in the trapperkeeper repo Change By: Chris Price Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Chris Price updated an issue Puppet / PUP-6698 Puppet server 2.5.0 does not properly handle exported file resources Change By: Chris Price Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Henrik Lindberg should we move this to your other epic as well? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price commented on PUP-6640 Re: The function generate() should merge stdout and stderr Confirmed the reproducer, moving this ticket to SERVER. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price commented on PUP-6640 Re: The function generate() should merge stdout and stderr bringing this in because it is closely related to SERVER-1570, so it seemed like it might be easy to fix while I still have some context around that code. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price assigned an issue to Chris Price Puppet / PUP-6640 The function generate() should merge stdout and stderr Change By: Chris Price Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price updated an issue Puppet / PUP-6640 The function generate() should merge stdout and stderr Change By: Chris Price Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price updated an issue Puppet / PUP-6640 The function generate() should merge stdout and stderr Change By: Chris Price Sub-team: emerald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6476) Add Hocon support to Puppet
Title: Message Title Chris Price updated an issue Puppet / PUP-6476 Add Hocon support to Puppet Change By: Chris Price Sprint: SE 2016-09-21 , SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6476) Add Hocon support to Puppet
Title: Message Title Chris Price assigned an issue to Henrik Lindberg Puppet / PUP-6476 Add Hocon support to Puppet Change By: Chris Price Assignee: Chris Price Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails The bug is in the Puppet Server ruby code, so, moving this ticket over to SERVER. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails Confirmed that I can repro using the steps described above; variable gets set to an empty string in Puppet Server, but an error is thrown when running via puppet apply. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: SE 2016-10- 19 05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: SE 2016-10-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price assigned an issue to Chris Price Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price updated an issue Puppet / PUP-6640 The function generate() should merge stdout and stderr Change By: Chris Price Sprint: SE 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: EP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Sprint: EP 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price updated an issue Puppet / PUP-6640 The function generate() should merge stdout and stderr Change By: Chris Price Sprint: EP 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price updated an issue Puppet / PUP-6640 The function generate() should merge stdout and stderr Change By: Chris Price Sprint: EP 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments
Title: Message Title Chris Price commented on PUP-731 Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments Henrik Lindberg isn't it also the case that in Puppet 3, ruby functions would be env-isolated as long as you didn't do anything fancy like define a ruby class or method inside your puppet function definition? (I know that's not a complete or acceptable solution, but since we seem to be enumerating the actual state of the issue here...) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6476) Add Hocon support to Puppet
Title: Message Title Chris Price assigned an issue to Chris Price Puppet / PUP-6476 Add Hocon support to Puppet Change By: Chris Price Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price assigned an issue to Chris Price Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Chris Price Assignee: Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Awesome, thanks for testing that, Thomas Hallgren. We have already updated to 1.7.26 in our master branch, and are in the process of doing long-running memory testing against it. As soon as that completes we'll be shipping OSS releases containing that version, so hopefully that'll take care of it. I'll make sure this comes up in triage so we can discuss test coverage. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Henrik Lindberg oh - I was assuming that the patch to Puppet could be applied for just the check on the environment directory, specifically. If that's not possible, and it would have to go into some generic filesystem handling code, then I would probably agree that we shouldn't do that. I expect that when we open the issue with JRuby, if there's a good reproducer included, they'll merge it very quickly; it's just that their release cadence has slowed down significantly for the 1.7.x branch. They'd probably get the fix out in JRuby9k within a week or two, but we can't use that yet. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions We've laid some initial groundwork for shipping JRuby from a fork, but we've never actually done it before, because they did a release of the things we needed before we finished ironing out the process. I'd prefer to avoid that except for a last-resort kind of situation; the build process for JRuby is pretty hairy and it seems like it wouldn't be too hard for us to screw something up This one seems like it'd be reasonably easy to solve in Ruby code, so maybe not worth those risks... WDYT? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6241) puppet agent ostensibly succeeds when environment directory has wrong permissions
Title: Message Title Chris Price commented on PUP-6241 Re: puppet agent ostensibly succeeds when environment directory has wrong permissions Thomas Hallgren I would say that it depends on the proposed solution. If we want to file a bug with upstream JRuby and wait for a release that contains that fix, then yes, our team should take it. But if we think this is too urgent to wait for (it will be several months before they do another release since they just did one last week), and we want to put a permissions check directory into the Puppet Ruby code in the interim, then maybe not? In fact, having thought about it for a second, it seems like perhaps the best thing to do would be to do both? So we could keep this ticket for a short-term fix in the Puppet codebase, and I will spin off a separate ticket about filing/tracking an upstream JRuby bug? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6640) The function generate() should merge stdout and stderr
Title: Message Title Chris Price commented on PUP-6640 Re: The function generate() should merge stdout and stderr David Kramer not that I'd be opposed to getting some extra eyes on it, but I know for sure that the code that's causing this is in the puppetserver repo. We had to provide a custom implementation of the Puppet::Utils::Execution stuff that would work on the JVM, and that's where the behavioral differences were introduced. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Chris Price assigned an issue to Unassigned Puppet / PUP-6275 Compiler PROFILE output should be logged at INFO level Change By: Chris Price Assignee: Chris Price 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-6275) Compiler PROFILE output should be logged at INFO level
Title: Message Title Chris Price commented on PUP-6275 Re: Compiler PROFILE output should be logged at INFO level For the profiler info that Charlie Sharpsteen is talking about, I think it ends up at debug level due to this line: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/http/handler.rb#L170 I have no objection to changing that; Charlie Sharpsteen perhaps you can confirm that changing that line will indeed give us the behavior that you are after? 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-6640) The function generate() should merge stdout and stdin
Title: Message Title Chris Price commented on PUP-6640 Re: The function generate() should merge stdout and stdin Fabien Wernli great, thanks for filing 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-6636) Puppet's fileserver seems to be unable to handle a path containing a directory called "environment"
Title: Message Title Chris Price moved an issue Puppet / PUP-6636 Puppet's fileserver seems to be unable to handle a path containing a directory called "environment" Change By: Chris Price Key: SERVER PUP - 1483 6636 Project: 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-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Chris Price Component/s: 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-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Chris Price commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails Fabien Wernli ok, thanks for the additional info. It definitely seems like it should throw an error if the exit code is non-zero, rather than returning an empty string. We'll try to look into that soon. I'm not sure if we have support for STDIN/STDOUT in the server implementation of Puppet::Util::Execution at the moment; can you provide an example use case for that? And maybe we should break that out into a separate ticket so that we can tackle them individually. 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-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Chris Price commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Stephano Zanzin can you clarify what you mean when you say "Puppet dashboard"? Henrik Lindberg does this error sound familiar at all? 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 Chris Price commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails Fabien Wernli When you say it works with "puppet agent 4.5.2", do you mean via 'apply'? Or, if you mean that it works with a agent/master setup, what sort of master are you using? 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 Chris Price updated an issue Puppet / PUP-6588 Allow context path in http_proxy Change By: Chris Price Scrum Team: Puppet Server Code Management 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 Chris Price commented on PUP-6588 Re: Allow context path in http_proxy Anderson Mills Jesse Scott this came up in our triage meeting, we think it probably belongs on your team, but feel free to re-assign if that's not correct. 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 caches the resultant values of functions defined purely in the puppet language
Title: Message Title Chris Price commented on PUP-6582 Re: The environment cache erroneously caches the resultant values of functions defined purely in the puppet language Chris Price Does puppet server have logic trying to figure out if one request will yield an identical catalog and then avoid compilation ? Definitely not. 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-6503) Types from invalid modules do not fail
Title: Message Title Chris Price updated an issue Puppet / PUP-6503 Types from invalid modules do not fail Change By: Chris Price Sprint: Server Emerald 2016-07-27 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-6503) Types from invalid modules do not fail
Title: Message Title Chris Price moved an issue Puppet / PUP-6503 Types from invalid modules do not fail Change By: Chris Price Key: SERVER PUP - 1417 6503 Project: 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-6492) Reports are not stored for current node
Title: Message Title Chris Price updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Chris Price Sprint: Server Emerald 2016-07-27 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-6492) Reports are not stored for current node
Title: Message Title Chris Price updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Chris Price Sub-team: emerald 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 (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price commented on HI-523 Re: Add support for using hocon for main hiera config file Alright, we just got off of a call with Nicholas Fagerlund and he helped us clarify our understanding of how all of this works. I think that as a result of that we landed basically where Henrik suggested: 1. We will not try to do anything for the old/hiera3 version of hiera.yaml that lives in the conf/codedir. 2. For environment/module versions of hiera.yaml, we were confused and thought that Puppet's hiera_config setting would come into play somehow. We now understand that it does not, and that the hiera.yaml filename is hard-coded into the data provider. So for this ticket, Jane Lu will add some logic that allows us to look for either hiera.conf or hiera.yaml in that directory, and parse the config accordingly. 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 (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price commented on HI-523 Re: Add support for using hocon for main hiera config file Jane Lu yes, based on the other thread, I think we would be using .conf here. Henrik Lindberg for the first stab at this I think we probably wouldn't be changing anything in packaging. We might not even change the search path stuff - we could just say "iff you set your hiera config path to a file that ends with .conf, we will attempt to parse it as HOCON. Hopefully the result of that would give us just a raw data structure (Ruby map) that we could pass along to the consuming code in just the same way that you currently parse the YAML into a map (before deciding whether it is v3 or v4). Does that sound tractable? I don't have any issue with not supporting hiera 3 config format in HOCON if there is a win to be had there, but it seems like if the steps are just: find config file parse into a map pass map to lookup code so it can decide what version it is and how to perform lookups Then the HOCON bit doesn't even really care whether we're talking about hiera 3 or 4? 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
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server This has also been requested internally by several parties, and in fact MEEP is using an unofficial version of this to implement its PE infrastructure configuration. 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server So I'll step back to be an ass and suggest: Why do we need to do this anyway? If Hiera is intended to read machine-optimized data files, what's wrong with JSON? I wouldn't describe hiera data files as "machine-optimized data files". I think that most users probably edit them by hand and maintain them in their VCS trees. We currently support both YAML and JSON for them, the user can choose, but we have gotten requests from the community to try to be more consistent about our config file formats, and in particular these files. (n fact this particular ticket was filed by an open source user.) Please don't do that. The conf.d/foo.conf pattern is clear and reasonable. That's fine by me; I have no intention of taking on that work unless UX initiates it. I'm mentioning it because users suggested it earlier in this ticket. 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 (HI-525) test coverage for hiera/lookup hocon support
Title: Message Title Chris Price commented on HI-525 Re: test coverage for hiera/lookup hocon support As this project was picked up opportunistically to take advantage of us having an intern available to work on it this summer, my hope is for this to not end up being disruptive to QA to whatever extent is possible. My personal opinion is that if we simply achieve the same level of coverage as what we currently have for yaml/JSON, that should be sufficient, and if others agree with that, we can probably just have the developers handle all of the work. If QA believes we need to increase the coverage beyond that, then we can discuss options in terms of ownership. 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Kylo Ginsberg thanks. J.D. Welch / Lori Landesman : do you have any input on this? Here's a tl;dr to save you reading through all of the comments: We are adding support for HOCON as an optional config file format for hiera and "puppet lookup" data files; this will be an opt-in thing that lives alongside our current support for YAML and JSON for these files. We have been using .conf as a file extension for HOCON files in all of the current places where we use HOCON in Puppet and PE, but there seems to be a consensus here that that would be a confusing suffix to use for the hiera data files, because they are not "config" files - they are data files - and the .conf extension feels like it implies that they are config files. So, we intend to use a .hocon extension for those data files. Unless either of you have any objections to the above, we'll proceed with that plan. Separately, we may want to have a discussion in the future about whether our existing HOCON config files in Puppet/PE should also be renamed from .conf to .hocon, but since that would be a costly and disruptive change, we do not intend to pursue it for now. 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
Jira (PUP-6476) Add Hocon support to Puppet
Title: Message Title Chris Price commented on PUP-6476 Re: Add Hocon support to Puppet HI-525 is where I started the conversation with Eric Thompson to try to sort out our QA / test coverage needs for this stuff. 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 (HI-525) test coverage for hiera/lookup hocon support
Title: Message Title Chris Price commented on HI-525 Re: test coverage for hiera/lookup hocon support Eric Thompson this is not urgent; our intern is working on some of these tickets as a summer project, and whenever you have a chance I'd be interested to hear if you have any thoughts about what level of test coverage might be necessary. 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 (HI-525) test coverage for hiera/lookup hocon support
Title: Message Title Chris Price created an issue Hiera / HI-525 test coverage for hiera/lookup hocon support Issue Type: Task Assignee: Unassigned Created: 2016/07/07 1:52 PM Priority: Normal Reporter: Chris Price We will have spec coverage for HI-341 and PUP-6476. Need to sync up with QA and determine whether there is existing beaker coverage for the YAML backends, and if so, consider adding coverage for HOCON as well. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (HI-524) determine strategy for something like eyaml for hocon
Title: Message Title Chris Price created an issue Hiera / HI-524 determine strategy for something like eyaml for hocon Issue Type: Task Assignee: Unassigned Created: 2016/07/07 1:49 PM Priority: Normal Reporter: Chris Price Lots of hiera users use eyaml to encrypt strings in their hiera files. Some questions: 1. Will this continue to be relevant given the "sensitive data" work that is underway? 2. If so, does eyaml work with the new puppet lookup stuff? How? 3. How much work would it be to provide similar tooling for encrypting fields in HOCON files? 4. This does not seem like something that would be necessary for an MVP, but is it something we'd want to consider building later? Or is it something that might emerge from the community if there's a strong demand for it? Add Comment
Jira (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price commented on HI-523 Re: Add support for using hocon for main hiera config file Henrik Lindberg awesome, thanks. We'll read up on this before doing any work on this ticket, and may have questions or responses to the comments you added above once we get there. 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 (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price commented on HI-523 Re: Add support for using hocon for main hiera config file Henrik Lindberg I didn't realize that the format had changed between "3" and "4". We (server devs) need to do some homework and reading before we actually consider starting work on this ticket. Are there docs somewhere that explain the differences between the old and new system? 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server The original decision to use `.conf` was probably because that is what the HOCON library assumes by default, and is the extension that most apps that consume HOCON use in the wild. It's fair to point out that that may or may not be a reasonable or compelling reason to use that extension for our files. However, there is a lot of prior art in the current Puppet products that uses that extension, so it would be non-trivial to change. My proposal for now would be: Use .hocon for the hiera data files because the points about those files being data rather than config seem compelling. Use .conf for any net-new config files that we add in the near term (assuming that they are actually config files). This will at least be consistent with all of the existing PE config files, and that seems like a better short-term strategy than introducing another discrepancy for facter and assuming we'll rename all of the other ones later. Spin off a separate ticket, probably directed towards the UX team, to consider the pros and cons of doing a sweeping rename of all of the existing hocon .conf files over to use .hocon, and if we decide to do that, do it all in one fell swoop. Thoughts? 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
Jira (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price commented on HI-523 Re: Add support for using hocon for main hiera config file ping Henrik Lindberg Kylo Ginsberg just for visibility. 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-6479) Update hocon gem version and packaging in puppet-agent
Title: Message Title Chris Price commented on PUP-6479 Re: Update hocon gem version and packaging in puppet-agent ping Kylo Ginsberg for visibility. 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 (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Chris Price created an issue Hiera / HI-523 Add support for using hocon for main hiera config file Issue Type: Task Assignee: Unassigned Created: 2016/07/07 10:24 AM Priority: Normal Reporter: Chris Price This is a follow-up to HI-341 and related tickets. After that work is completed, we will have the ability to use HOCON for hiera data files, but the main hiera config file will still be expressed as YAML. It would be nice to optionally support HOCON for the main hiera config as well. In order to do this in a backward-compatible way, we should probably try to alter the logic that currently loads the hiera.yaml file so that it looks first for a hiera.conf file, and if it finds it, parses it as HOCON. If it doesn't find it, it should fall back to the current logic for reading the YAML file. There will probably be changes required in both the hiera and puppet projects to achieve this; after we investigate a bit further, it might be reasonable to create a separate PUP ticket for those changes. Add Comment
Jira (PUP-6479) Update hocon gem version and packaging in puppet-agent
Title: Message Title Chris Price created an issue Puppet / PUP-6479 Update hocon gem version and packaging in puppet-agent Issue Type: Task Assignee: Unassigned Created: 2016/07/07 9:59 AM Priority: Normal Reporter: Chris Price This is blocked by RE-7610, and probably blocks the merge of HI-341 and PUP-6476. Once we have a strategy for how to package gems that are needed by both the agent and Puppet Server, we need to modify the existing packaging setup for puppet-agent to leverage this strategy for deploying the hocon gem. We also need to bump the version number of that gem up to 1.1.1, which contains a bugfix necessary for the Hiera integration. Add Comment This message was sent
Jira (PUP-6476) Add Hocon support to Puppet
Title: Message Title Chris Price commented on PUP-6476 Re: Add Hocon support to Puppet Henrik Lindberg thanks for creating this ticket. Is this something that you expect the language team will be taking on, or would it be appropriate for us to assign it to Jane Lu as a follow-up task to her Hiera PR? 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Henrik Lindberg - thanks for creating that other ticket. I'll add some comments over there. Henrik Lindberg & R.I.Pienaar - what you are saying about the .conf extension not making sense for data files does resonate with me... that was part of the reason why we used .hocon for the original PR. Kylo Ginsberg does this sway your opinion at all? Henrik Lindberg - agreed, will create a separate ticket re: the main hiera.yaml config file. 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Kylo Ginsberg - cool - I agree with both of those and thanks for the heads up re: puppet. 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server Henrik Lindberg Just FYI, I'm still planning on creating a ticket to add the same capability to the lookup type soon, and we'll pick that up after we work out all of the kinks on the hiera one. A few random UX questions on this: 1. What file extension should we use for hocon files? We've been using .conf everywhere else that we've been using HOCON, so my inclination is to stick with that. Alternately, we could use .hocon to make it more explicit, but that seems inconsistent. A third option would be to try to support both. Henrik Lindberg / Kylo Ginsberg / Lori Landesman / J.D. Welch : any opinions? 2. Should we also try to add support for (optionally) having a hiera.conf file instead of hiera.yaml file? Seems inconsistent to only support it for the data but not for the main config file. If there is consensus that we should try to do that, I'll carve a separate ticket for that as well. /cc Eric Sorenson - you may also have opinions on these topics. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Henrik Lindberg I'm going to move this over to SERVER since it seems highly likely that the JRuby issue is what's going on here. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Matthew Nicholson great, thanks for confirming. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Matthew Nicholson do you also have hiera lookups in your catalogs, which may be looking up undefined variables? 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 (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Chris Price updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Chris Price Scrum Team: 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar I found a code path in the JRuby code that might explain it. There is a method called org.jruby.Ruby#getCurrentContext, which gets called from lots and lots of places. Its call stack ends up checking for the existence of a soft reference of a context object that would contain the current RubyThread object, and if that reference has been cleared out by GC, then it calls an adopt method to "adopt" the current Java thread, which ultimately results in the construction of a new RubyThread instance. If you have enough load on your server, and a small enough heap size, it may be garbage collecting these SoftReferences frequently enough to trigger this code path and I think that would explain it. Jeremy Barlow can you think of any easy way to use jmap or some other tool to watch the instances of org.jruby.runtime.ThreadContext to confirm or refute the theory that the SoftReferences are being GC'd? Or, based on your recent work do you have any suggestions about how to force GC of SoftReferences in a reproducer program? 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar The timeout code does appear to use Java threads behind the scenes, but I don't see anywhere where it is creating another instance of one of these special RubyThread objects, and it seems like those objects are the ones that would have the offending object ID on them. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar One thing I notice is that some of the obvious places where JRuby ends up creating these thread objects is in calls to `popen3`, so I'd be curious whether or not you happen to be using that or similar methods for launching external processes in any of your modules? 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Jürgen Thomann when this begins to happen to you, does it affect 100% of the catalog compilations that are looking up an undefined variable? Or is it only a subset of them? I'm poking around in this JRuby code, trying to think of a way that I can write a more reliable reproducer, and it's weird to me that the exception seems like it may be related to a RubyThread object, when we shouldn't be using any threads inside of the JRuby containers. It seems like generating a bunch of ruby objects in order to get that ObjectId counter into the "too high" territory will be easy, but it seems like after that I have to figure out how to cause a new RubyThread to be allocated. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Yes, thank you Jürgen Thomann! I'll keep an eye on that JRuby ticket, and also read through this code again to see if it gives me a better idea of how to come up with a local reproducer so that we can confirm the JRuby fix when it goes in. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar I left my local repro attempt running for about 3 days and wasn't able to repro. So, I guess, Jürgen Thomann, if you are willing to try that suggestion about the ruby patch and the admin endpoint for flushing, let me know how it goes. If we don't get any actionable info then I can look into putting together a custom .jar file for you that adds some instrumentation to the JRuby code, and maybe that'll help us figure it out? 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Jürgen Thomann oh, I didn't realize we shipped our default auth.conf in a way where that was disabled. Not sure if we did that intentionally. No way to trigger that action w/o hitting the HTTP endpoint, unfortunately. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Jürgen Thomann how did you disable the admin api? If you want to email me, my email address is just chris at puppet dot com. I'd be happy to take a look at the heap dump. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar I left my reproduction attempt running overnight and it does not seem to have repro'd for me. I guess I will leave it running for a while longer and see what happens. If we can come up with an in-house reproducer I have a lot of ideas about how to debug this; if we can't, we might end up having to do something like create an instrumented build of JRuby and package it up to run in a user environment, which will be a lot more work for everyone 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title
Chris Price commented on PUP-6409
Re: "integer too big to convert to `int' at" with lookupvar
Jürgen Thomann A heap dump wouldn't hurt - what is your max heap size set to?
If we're unable to come up with a reliable reproducer on our end, then our best chance of tracking this down is probably to have you add a few debug print statements to the Puppet Ruby code itself.
If you could edit `puppet/parser/scope.rb`, around line 520, and change this:
begin
throw(:undefined_variable, reason)
rescue UNCAUGHT_THROW_EXCEPTION
to something like:
begin
Puppet.warning(" About to throw undef var exception! Reason: '#{reason}' (class: '#{reason.class}') (inspect: '#{reason.inspect}')")
throw(:undefined_variable, reason)
rescue UNCAUGHT_THROW_EXCEPTION
Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title
Chris Price commented on PUP-6409
Re: "integer too big to convert to `int' at" with lookupvar
Henrik Lindberg that's an interesting thought.
Jürgen Thomann you said that {{ inline_template("<%= scope.lookupvar('::missing_variable') %>') }} will reliably reproduce it for you once your server is in this state? If so I'll change my reproduction attempt to use that exact string.
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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Henrik Lindberg thanks. I'll look into that if I get a second. Meantime I spun up a puppet server locally that calls inline_template from site.pp and does a lookup on an invalid var in there; set up a curl script to loop making catalog requests against it. Has been running for a few hours now with no repro, will probably leave it running overnight if it hasn't repro'd before EOB. 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-6409) "integer too big to convert to `int' at" with lookupvar
Title: Message Title Chris Price commented on PUP-6409 Re: "integer too big to convert to `int' at" with lookupvar Henrik Lindberg is it possible to write a small ruby driver program that uses Puppet as a library and just executes a Puppet function? Assuming that the answer is "yes", do you have an example somewhere of how to do that? 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-6401) deprecated symbol monkey patch code path is always executed when running puppet under jruby
Title: Message Title Chris Price commented on PUP-6401 Re: deprecated symbol monkey patch code path is always executed when running puppet under jruby I think that because of the way our settings work (does this sound like a familiar refrain, Kylo Ginsberg ), it would be hard to make the application of the monkey patch conditional on the value of that setting, because you won't know the value of that setting until all of the settings have been fully initialized. 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-6401) deprecated symbol monkey patch code path is always executed when running puppet under jruby
Title: Message Title Chris Price commented on PUP-6401 Re: deprecated symbol monkey patch code path is always executed when running puppet under jruby Henrik Lindberg the other observation that I meant to include in my original write-up of this but forgot was this: That "ArgumentError" appears to be getting caught by some other part of the system. I did some tests where I tried to set "strict" to :error, and was not able to cause a fatal error. This may have been in part because a lot of the code paths that trigger this code happen during the very early stages of initialization, when the settings are not yet fully initialized. Another experiment that I did was to comment out the case statement and simply have that monkey patch code always raise the ArgumentError if the type check failed, and this did not appear to cause a fatal error either. The system would simply log the deprecation warning and continue initialization and start up successfully. Kylo Ginsberg this isn't really causing a huge problem atm but we might need to decide what we want to do here; it sounds like from what Henrik Lindberg is saying that it is probably untenable for us to fix our internal code up to avoid it triggering this code path, which means that we are always going to be logging the deprecation warning... but that kind of means that whenever we do try to remove the monkey patch we aren't necessarily going to have given users any kind of real warning about it going away. If that's the case then it seems like maybe we should just not be logging the warning at all, and/or we should just go ahead and remove the monkey patch entirely... but I don't recall what chain of events led us to putting the monkey patch back in in the first place. 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
Jira (PUP-6401) deprecated symbol monkey patch code path is always executed when running puppet under jruby
Title: Message Title Chris Price commented on PUP-6401 Re: deprecated symbol monkey patch code path is always executed when running puppet under jruby ping Kylo Ginsberg @henrik - would appreciate it if someone on your end could validate that you can repro this, and then maybe we can talk about what the fix should be. 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-6401) deprecated symbol monkey patch code path is always executed when running puppet under jruby
Title: Message Title
Chris Price commented on PUP-6401
Re: deprecated symbol monkey patch code path is always executed when running puppet under jruby
Here is a branch where I've added some print statements to the symbol monkey patch:
https://github.com/cprice404/puppet/tree/scratch/master/PUP-6401-symbol-deprecation-under-jruby-example
With these changes, if you attempt to start webrick under JRuby, you will see a ton of print output indicating places where the comparator is being called when it wouldn't be under MRI.
Also, when running under Puppet Server, we do get warn messages logged from the pops/type.rb; when attempting to start webrick under JRuby those warn-level log messages do not show up, even though "puts" output does. I haven't figured out why yet; it may be because of the fact that we are using a symbol equality comparison inside of the implementation of symbol equality comparison :
(I'm referring to the "case" statement on Puppet[:strict] below.)
class Symbol
def <=> (other)
puts "SYMBOL COMPARISON: '#{self}' (#{self.class}), '#{other}' (#{other.class})"
if (other.class != Symbol)
case Puppet[:strict]
when :warning
Puppet.warn_once('deprecation', 'symbol_comparison', 'Comparing Symbols to non-Symbol values is deprecated')
Jira (PUP-6401) deprecated symbol monkey patch code path is always executed when running puppet under jruby
Title: Message Title Chris Price created an issue Puppet / PUP-6401 deprecated symbol monkey patch code path is always executed when running puppet under jruby Issue Type: Bug Assignee: Unassigned Created: 2016/06/10 3:58 PM Priority: Normal Reporter: Chris Price It appears that JRuby calls the <=> operator for any equality comparisons for Symbol objects. Because of this, our monkey patch for symbol comparisons (which logs a deprecation warning) gets triggered for dozens of equality comparisons that happen under normal Puppet operation, when running under JRuby. (It does not appear that the normal Puppet code triggers the deprecated code path under MRI.) The monkey patch is here: https://github.com/puppetlabs/puppet/blob/743255d25d5a3c59f58328fa51af0bc1299f5a0b/lib/puppet/util/monkey_patches.rb#L21-L37 This is an example of a few lines of code that trigger this comparison in JRuby: https://github.com/puppetlabs/puppet/blob/743255d25d5a3c59f58328fa51af0bc1299f5a0b/lib/puppet/pops/types/types.rb#L649-L650 Add Comment
