Jira (PDOC-60) Strings skips docs for the log message functions
Title: Message Title William Hopper commented on PDOC-60 Re: Strings skips docs for the log message functions Jesse Scott came up with a few options for this today. On Monday we'll see what Henrik Lindberg thinks of them. 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 (FACT-1507) acceptance: test fact blocklist in config file
Title: Message Title Glenn Sarti commented on FACT-1507 Re: acceptance: test fact blocklist in config file Merged into master at; https://github.com/puppetlabs/facter/commit/454977078a4dfdf16e5a9f5052407a692658f39a 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-6738) Update version post Agent 1.7.0 release
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-6738 Update version post Agent 1.7.0 release Change By: Sean McDonald Assignee: Sean McDonald 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-6738) Update version post Agent 1.7.0 release
Title: Message Title Sean McDonald created an issue Puppet / PUP-6738 Update version post Agent 1.7.0 release Issue Type: Task Assignee: Sean McDonald Created: 2016/09/23 3:10 PM Priority: Normal Reporter: Sean McDonald Update the reported version from 4.7.0 to 4.7.1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Kylo Ginsberg Assignee: Sean McDonald Kylo Ginsberg 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-3068) Make sure we have full-stack retry->dlo test(s)
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3068 Make sure we have full-stack retry->dlo test(s) Issue Type: Improvement Assignee: Unassigned Created: 2016/09/23 2:35 PM Priority: Normal Reporter: Rob Browning Make sure we have reasonable full stack (i.e. testing a pdb-instance via http) testing of the command retry behavior, particularly in the complete failure, "winds up in the dlo" case. https://github.com/puppetlabs/puppetdb/pull/2061#discussion_r79942300 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6724) The new strftime function is not compatible with the strftime function in stdlib.
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6724 The new strftime function is not compatible with the strftime function in stdlib. Change By: Moses Mendoza Priority: Normal Blocker 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-6714) PCore generation omits information about capability types
Title: Message Title Thomas Hallgren commented on PUP-6714 Re: PCore generation omits information about capability types Chris Cowell, the ticket is in progress with an estimate of 2 story points. I can't give you a closer estimate than that. 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-6723) collector_transformer: negation query for array type properties is broken
Title: Message Title Henrik Lindberg commented on PUP-6723 Re: collector_transformer: negation query for array type properties is broken Isaiah Frantz Thanks for doing some detective work and finding that (as I suspected) making the change would be a breaking thing. IMO, the fact that == acts as in is a bad thing and should really be changed as there is no way to ask for an exact match. 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-6723) collector_transformer: negation query for array type properties is broken
Title: Message Title Isaiah Frantz commented on PUP-6723 Re: collector_transformer: negation query for array type properties is broken ehh, I just reread the docs and it does say that != only matches if the value of the attribute is identical to the term and that if the value of the attribute is an array it will always match Bring on the in! 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-6723) collector_transformer: negation query for array type properties is broken
Title: Message Title Isaiah Frantz commented on PUP-6723 Re: collector_transformer: negation query for array type properties is broken Changing it to "in" would make the functionality more obvious and would keep from breaking old code. I think that it would be wise to, with your suggestion and mine, fail if an array type is being used in a collector using != since it is not obvious that this shouldn't work in the opposite way that the == case does. Also, the docs dont mention anything about the current behaviour. They only say that you cant use an array as the search term, nothing about an array type property in a negation. 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-3067) Switch command logging from message id to '-'
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3067 Switch command logging from message id to '-' Issue Type: Task Assignee: Unassigned Created: 2016/09/23 11:58 AM Priority: Normal Reporter: Ryan Senior Before stockpile we would generate a UUID when the command was received and enqueue that with the message in ActiveMQ. We're no longer doing that with stockpile and a good alternative is the message id from stockpile AND the recieved time (milliseconds since epoch). This identifier will be unique across restarts and can optionally be used to find the command on disk later. This ticket should also include an audit of our logging to sprinkle this in the other places that it's needed. Add Comment
Jira (PUP-6706) Add Binary type to Puppet Serialization
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6706 Add Binary type to Puppet Serialization Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6701 PE Everett fails to install: Unknown function: 'puppetdb_query' Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6705) Add Sensitive type to Puppet Serialization
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6705 Add Sensitive type to Puppet Serialization Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-5831) Add a Binary type and runtime object
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5831 Add a Binary type and runtime object Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6689) Timespan and Timestamp should inherit from Scalar, not from Numeric
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6689 Timespan and Timestamp should inherit from Scalar, not from Numeric Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6682) $settings leaks symbols into manifests
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6682 $settings leaks symbols into manifests Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6291) Add 'abs' support to Numeric.new
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6135) change type mismatch errors in past tense to present tense
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6693) Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6693 Warn/error if $trusted_server_data is assigned if not in --trusted_server_facts mode and --strict is on Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6685) Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6685 Remove underscore from Timespan/Timestamp milli_seconds, micro_seconds, and nano_seconds Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6686) Timespan sometimes parses fractions incorrectly.
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6686 Timespan sometimes parses fractions incorrectly. Change By: William Hopper Status: Ready for CI Test Assignee: qa 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-6714) PCore generation omits information about capability types
Title: Message Title Chris Cowell commented on PUP-6714 Re: PCore generation omits information about capability types Thomas Hallgren Do we have an ETA on this? 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 (PDOC-60) Strings skips docs for the log message functions
Title: Message Title William Hopper commented on PDOC-60 Re: Strings skips docs for the log message functions Henrik Lindberg makes sense - the only problem there is that create_logging_functions is private, so YARD won't pick it up 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 (FACT-1512) Add command line flags related to fact blocking
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1512 Add command line flags related to fact blocking Change By: Maggie Dreyer Acceptance Criteria: * A command line flag allows the user to see all blockable fact groups *A command line flag allows the user to disable fact blocking for the current run Story Points: 2 Summary: Add a command line flag flags related to list all blockable fact groups blocking Currently, the names of various blockable fact groupings (one per resolver) are not discoverable to a user of Facter, but flagging facts to be blocked relies on these strings. We should add a command line option to Facter to print out all the fact groups available for blocking. We may also want to consider listing which facts are associated with each group.Note: this is a subset of the list of cacheable facts. Blocking is currently only enabled for a small number of fact groups. Also, add a flag to allow disabling fact blocking. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1512) Add command line flags related to fact blocking
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1512 Add command line flags related to fact blocking Change By: Maggie Dreyer Assignee: Maggie Dreyer 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-6736) PUP tests fail with 'pathspec '$COMPONENT_COMMIT' did not match any file(s) known to git'
Title: Message Title Moses Mendoza commented on PUP-6736 Re: PUP tests fail with 'pathspec '$COMPONENT_COMMIT' did not match any file(s) known to git' This appears to have been resolved by rerunning the pipeline. it's possible the failed run was triggered with incorrect parameters? successful run: https://jenkins.puppetlabs.com/job/platform_puppet_pkg-van-ship_master/ 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-6724) The new strftime function is not compatible with the strftime function in stdlib.
Title: Message Title Henrik Lindberg commented on PUP-6724 Re: The new strftime function is not compatible with the strftime function in stdlib. merged to master at: bda2f03 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-6724) The new strftime function is not compatible with the strftime function in stdlib.
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-6724 The new strftime function is not compatible with the strftime function in stdlib. Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-6592) acceptance: Sensitive data
Title: Message Title Henrik Lindberg commented on PUP-6592 Re: acceptance: Sensitive data No particular reason as I recall. Feel free to bring it in if that makes sense. 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-6724) The new strftime function is not compatible with the strftime function in stdlib.
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6724 The new strftime function is not compatible with the strftime function in stdlib. Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.
Title: Message Title Sven Mueller updated an issue Puppet / PUP-2790 if initctl --version doesn't list a matching string, upstart service provider fails badly. Change By: Sven Mueller Affects Version/s: PUP 4.5.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-2790) if initctl --version doesn't list a matching string, upstart service provider fails badly.
Title: Message Title Sven Mueller commented on PUP-2790 Re: if initctl --version doesn't list a matching string, upstart service provider fails badly. Just a quick update: I currently don't have any time to work on a pull request. However, using "/sbin/init --version" instead of "/sbin/initctl --version" works fine for us, also during installations, when initctl, status, start, ... are all overridden. telinit apparently (from my older comments) would also work, but I didn't check that on newer versions of upstart. 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-6724) The new strftime function is not compatible with the strftime function in stdlib.
Title: Message Title Henrik Lindberg commented on PUP-6724 Re: The new strftime function is not compatible with the strftime function in stdlib. Brandon High The problem with strftime does not exist in Puppet < 4.8.0 (and thus not in Davis). It will be fixed in Puppet 4.8.0 before Everett is released. 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-6724) The new strftime function is not compatible with the strftime function in stdlib.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6724 The new strftime function is not compatible with the strftime function in stdlib. Change By: Henrik Lindberg Fix Version/s: PUP 4.8.0 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-6723) collector_transformer: negation query for array type properties is broken
Title: Message Title Henrik Lindberg commented on PUP-6723 Re: collector_transformer: negation query for array type properties is broken Even if it can be argued that given that x == y is the equivalence of x in y and x != y is the equivalence of not x in y it is still a breaking change if the current behavior is not a regression. In general, the query capabilities inside of the collectors are weak (and poorly specified) and behave slightly differently for collection of virtual and exported resources. This is a long standing issue. For exported resources there is now a better query API, but there is no similar API for virtual resources. A complaint is also that the only thing you can do is to realize or override those resources. I added this ticket to our Triage, which means that it is something we need to discuss. Changes in this area may affect other components as well (notably puppet db). I am more inclined to add support for in, thus enabling not x in y than expanding on the IMO misuse of the == operator. It makes a lot more sense for the query operators to behave exactly like the corresponding operators in puppet. A complicating factor is that the compiler / resource framework equates an array of one element with a non array value. This makes it very hard to reason about the data type and what the operators mean - even harder when negating. 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 (PDOC-60) Strings skips docs for the log message functions
Title: Message Title Henrik Lindberg commented on PDOC-60 Re: Strings skips docs for the log message functions Another possible approach is to use yard meta tags on the create_logging_functions method in static_loader.rb. And then get yard to scan and process those. Making them be free standing 3.x or 4.x functions (like all others) would work, but is not the best approach since the static loader is a bit special and we have no mechanism for directing functions being autoloaded to end up in the static loader. (just some thoughts) 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 (FACT-901) Intermittent Unit Test failure
Title: Message Title Geoff Nichols commented on FACT-901 Re: Intermittent Unit Test failure There have been no updates on this ticket in over a year, so this is probably safe to close. If this is still an issue, we can re-open. 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.
