Jira (PUP-7155) PCore resource output improperly quoted
Title: Message Title Thomas Hallgren assigned an issue to Josh Cooper Puppet / PUP-7155 PCore resource output improperly quoted Change By: Thomas Hallgren Assignee: Thomas Hallgren Josh Cooper 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-4078) puppet resource tool output contains incorrect quoting
Title: Message Title Thomas Hallgren commented on PUP-4078 Re: puppet resource tool output contains incorrect quoting That explains it. Thanks Josh Cooper. 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-7155) PCore resource output improperly quoted
Title: Message Title Henrik Lindberg commented on PUP-7155 Re: PCore resource output improperly quoted Well: the %p uses u escapes to ensure that the output text works irrespective of encoding of the result. If not having the required font the output would be some kind of turd or space (or nothing). the output produced by %p is programmatic - i.e. it is in Puppet Language source form - if output should be the text it should be parsed and then written to IO. However, given that we have specified that all content read and written by Puppet is UTF-8 there is no real harm changing the string %p format (the occasional turd output does not really count as harmful). 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Tim Sharpe created an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Issue Type: Bug Assignee: Unassigned Created: 2017/06/07 1:52 AM Environment: Windows 10 Pro 64bit Priority: Normal Reporter: Tim Sharpe I was investigating why David Schmitt and I were getting different results from `Puppet::FileSystem.symlink` on Windows. His VM was correctly reporting an error and mine was silently failing. When run as a non-administrator user on my VM, `CreateSymbolicLinkW` would return non-zero (success for this function) when it should have failed. Going through the MSDN docs, I noticed that it returns a 1 byte `BOOLEAN` rather than the 4 byte `BOOL` that it is currently prototyped for with FFI (so I was getting a value with random data in the 3 upper bytes). Changing the FFI prototype for the function over to returning an `int8` resolved the problem for me (see linked PR). Add Comment
Jira (PUP-7620) Add a `unique` function that works with all kinds of iterables
Title: Message Title Henrik Lindberg commented on PUP-7620 Re: Add a `unique` function that works with all kinds of iterables Will add it to current sprint if we have time to add this - otherwise slip this to later release. 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-7155) PCore resource output improperly quoted
Title: Message Title Henrik Lindberg commented on PUP-7155 Re: PCore resource output improperly quoted Change that outputs unicode characters instead of u escapes merged to 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-7155) PCore resource output improperly quoted
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7155 PCore resource output improperly quoted Change By: Henrik Lindberg Assignee: Josh Cooper 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-7382) Ensure current values are YAML serializable
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7382 Ensure current values are YAML serializable Change By: Henrik Lindberg Assignee: Josh Cooper 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-7620) Add a `unique` function that works with all kinds of iterables
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7620 Add a `unique` function that works with all kinds of iterables 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-7615) puppet command leaks module command issues.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7615 puppet command leaks module command issues. Change By: Henrik Lindberg Assignee: 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-7615) puppet command leaks module command issues.
Title: Message Title
Henrik Lindberg assigned an issue to Henrik Lindberg
Puppet / PUP-7615
puppet command leaks module command issues.
Change By:
Henrik Lindberg
Assignee:
Adam Buxton Henrik Lindberg
Acceptance Criteria:
That it is possible to squelch warnings about faulty metadata.json
Sub-team:
Language
Story Points:
1
Release Notes Summary:
Warnings from faulty metadata.json can now be turned off by setting {{\--strict=off}}.
Team:
Agent
Sprint:
Agent 2017-06-14
Release Notes:
New Feature
Fix Version/s:
PUP 5.0.0
Component/s:
PE
Issue Type:
Jira (PUP-7615) puppet command leaks module command issues.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7615
puppet command leaks module command issues.
Change By:
Henrik Lindberg
when invoking {code} $ puppet facts (and various utils)Warning: vosp_wls has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at '], "data_provider": null}'Warning: wls_helpers has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at '{"name":"puppetlabs-lvm","version_requirement":">= 0.7.0"} ], "data_provider": null}'Warning: vosp_wls has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at '], "data_provider": null}'Warning: wls_helpers has an invalid and unparsable metadata.json file. The parse error: 399: unexpected token at '{"name":"puppetlabs-lvm","version_requirement":">= 0.7.0"} ], "data_provider": null}' {code} These appear to be bleed from what I would expect in puppet module list can or should these be quashed in other utilities.
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-7620) Add a `unique` function that works with all kinds of iterables
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7620 Add a `unique` function that works with all kinds of iterables Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-7579) Tags do not support UTF-8 characters
Title: Message Title Henrik Lindberg commented on PUP-7579 Re: Tags do not support UTF-8 characters We also need to make sure that collection results are sane when querying on a tag with lower/uppercase international characters and that the same result is obtained from virtual and exported collection. In PUP-6772 I voted against unicode in tags because of the many corner cases caused by different support for Unicode in MRI < 2.4.1 and that we are not yet on JRuby 9000. While the fix here makes it possible to stick unicode chars into a tag - it really needs to work throughout the entire ecosystem. 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-3204) Users and groups created mid-transaction are not found
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3204 Users and groups created mid-transaction are not found Change By: Geoff Nichols Issue Type: Bug New Feature 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-3204) Find LDAP users and groups created mid-transaction.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3204 Find LDAP users and groups created mid-transaction. Change By: Geoff Nichols Summary: Users Find LDAP users and groups created mid-transaction are not found . 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-7255) SPIKE: Gracefully fail or downgrade when newer agents to talk to older masters
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7255 SPIKE: Gracefully fail or downgrade when newer agents to talk to older masters Change By: Eric Delaney QA Risk Assessment Reason: This is a spike we should decide what/how to test based on the follow on tickts QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney 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-7628) Cannot provision compile masters outside production environment
Title: Message Title Jeremy Barlow commented on PUP-7628 Re: Cannot provision compile masters outside production environment Thanks, Dylan Ratcliffe. That makes sense. Given that this issue spans more conditions than just the startup of a Puppet master - e.g., various puppet CLI commands - I moved this ticket over to the PUP project for better visibility across the platform teams - and for open-source users. The ticket is now PUP-7628. 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-7628) Cannot provision compile masters outside production environment
Title: Message Title Jeremy Barlow moved an issue Puppet / PUP-7628 Cannot provision compile masters outside production environment Change By: Jeremy Barlow Affects Version/s: PE 2017.2.1 Component/s: puppet Component/s: Puppet Server Key: PE PUP - 20873 7628 Project: Puppet Enterprise [Internal] 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 g
Jira (PUP-7628) Cannot run puppet commands or startup master when environment directory missing
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-7628 Cannot run puppet commands or startup master when environment directory missing Change By: Jeremy Barlow Summary: Cannot provision compile masters outside production run puppet commands or startup master when environment directory missing 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-7628) Cannot run puppet commands or startup master when environment directory missing
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-7628 Cannot run puppet commands or startup master when environment directory missing Change By: Jeremy Barlow Sprint: Server 2017-07-26 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-2280) If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-2280 If a resource is triggered by a refresh, and it fails, puppet doesn't treat it as a failure Change By: Maggie Dreyer Sprint: Puppet 5 Race to the Finish! Agent 2017-06-14 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-7155) PCore resource output improperly quoted
Title: Message Title Josh Cooper commented on PUP-7155 Re: PCore resource output improperly quoted If not having the required font the output would be some kind of turd or space (or nothing). There's a difference between preserving the unicode character for a given locale vs trying to correctly display unicode characters across multiple locales. For us, it's important that we preserve the unicode character end-to-end (agent-server-puppetdb-console). Depending on the browser, font, Accept-Language headers, etc the result may not be rendered correctly, but there's no much we can do there. However, given that we have specified that all content read and written by Puppet is UTF-8 That's not entirely true as we still support binary data in a PSON catalog. We need to provide binary data type support end-to-end so we can get rid of PSON in puppet 6. 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-5893) Add tree iterative functions - tree_each, and tree_reduce
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5893
Add tree iterative functions - tree_each, and tree_reduce
Change By:
Henrik Lindberg
BackgroundAt the moment it is difficult to flatten out a complex structure. There is a flatten in standard lib that creates a flat copy of a tree of {{Array}} objects, and it errors if given a Hash. If the restriction was lifted to also support Hash, Ruby flatten method flattens a hash by making an array of keys and values. That makes the result hard to use if it is a mix of arrays and hashes.It is very useful to be able to iterate over such a tree instead of creating a copy, and it is of value to iterate over it in different ways. This is what the flat_each does.To describe what is wanted; imagine he the two functions {{ each_element }} , and {{ each_container }} (these are not the functions we want at the end; they are too special, but they serve as illustration). {{ each_element(Iterable $x) }} This function visits each container and leaf in the tree $x and calls a given block with 1.3 parameters. The block gets container, index, and value if defining three parameters, if using 2 arguments the container and index is delivered as a tuple, and if using 1 arg the three args are delivered as a Triple. The first yielded value is the given argument value. Each element in the tree is yielded with parent before children, depth first.When not given a block, each_element produces an Iterator that yields a triplet. {{ each_container(Iterable $x) }} This function is he same as to each_element but skips children that are not containers. This enables doing inner loops conditionally.What we should do instead is to first implement {{next()}} since that makes it possible to do general skipping and pruning; {{next(true)}} means skip this element and its children and {{next()}}, or {{next(false)}} to mean "do not prune", take next element I am done with the one you just gave me.ProposalImplement flat_each such that:* It accepts an Iterable and a required block* It produces an Iterator if not given a block* When given a block, it produces the given first argument* It yields 1-3 arguments as described for each_element* The value produced by the block is ignored (as for a regular each)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.Implement flat_reduce such that:* It accepts an Any and a required block* if value is not Iterable, the given value is yielded and nothing more, else every value in the iterable is yielded to the block* It produces an Iterator if not given a block* When given a block, it produces a result that is determined by the block** For each given container* It yields up to 6 arguments, exact rules t.b.d (see below)* The value produced by the block represents the next state (see below)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.* In contrast to the existing {{reduce}} the {{flat_reduce}} does not take an optional starting value, as that is controlled via the $direction.Example:{code:puppet}$a_tree.flat_reduce |$tree, $level, $direction, $container, $key, $
Jira (PUP-5893) Add tree iterative functions - tree_each, and tree_reduce
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5893
Add tree iterative functions - tree_each, and tree_reduce
Change By:
Henrik Lindberg
BackgroundAt the moment it is difficult to flatten out a complex structure. There is a flatten in standard lib that creates a flat copy of a tree of {{Array}} objects, and it errors if given a Hash. If the restriction was lifted to also support Hash, Ruby flatten method flattens a hash by making an array of keys and values. That makes the result hard to use if it is a mix of arrays and hashes.It is very useful to be able to iterate over such a tree instead of creating a copy, and it is of value to iterate over it in different ways. This is what the flat_each does.To describe what is wanted; imagine the two functions {{each_element}}, and {{each_container}} (these are not the functions we want at the end; they are too special, but they serve as illustration).{{each_element(Iterable $x)}}This function visits each container and leaf in the tree $x and calls a given block with 1.3 parameters. The block gets container, index, and value if defining three parameters, if using 2 arguments the container and index is delivered as a tuple, and if using 1 arg the three args are delivered as a Triple. The first yielded value is the given argument value. Each element in the tree is yielded with parent before children, depth first.When not given a block, each_element produces an Iterator that yields a triplet.{{each_container(Iterable $x)}}This function is he same as to each_element but skips children that are not containers. This enables doing inner loops conditionally.What we should do instead is to first implement {{next()}} since that makes it possible to do general skipping and pruning; {{next(true)}} means skip this element and its children and {{next()}}, or {{next(false)}} to mean "do not prune", take next element I am done with the one you just gave me.ProposalImplement flat_each such that:* It accepts an Iterable and a required block* It produces an Iterator if not given a block* When given a block, it produces the given first argument* It yields 1-3 arguments as described for each_element* The value produced by the block is ignored (as for a regular each)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.Implement flat_reduce such that:* It accepts an Any and a required block* if value is not Iterable, the given value is yielded and nothing more, else every value in the iterable is yielded to the block* It produces an Iterator if not given a block* When given a block, it produces a result that is determined by the block** For each given container* It yields up to 6 arguments, exact rules t.b.d (see below)* The value produced by the block represents the next state (see below)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.* In contrast to the existing {{reduce}} the {{flat_reduce}} does not take an optional starting value, as that is controlled via the $direction.Example:{code:puppet}$a_tree.flat_reduce |$tree, $level, $direction, $container, $key, $val | { ... }$tree is th
Jira (PUP-5893) Add tree iterative functions - tree_each, and tree_reduce
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5893
Add tree iterative functions - tree_each, and tree_reduce
Change By:
Henrik Lindberg
BackgroundAt the moment it is difficult to flatten out a complex structure. There is a flatten in standard lib that creates a flat copy of a tree of {{Array}} objects, and it errors if given a Hash. If the restriction was lifted to also support Hash, Ruby flatten method flattens a hash by making an array of keys and values. That makes the result hard to use if it is a mix of arrays and hashes.It is very useful to be able to iterate over such a tree instead of creating a copy, and it is of value to iterate over it in different ways. This is what the flat_each does.To describe what is wanted; imagine the two functions {{each_element}}, and {{each_container}} (these are not the functions we want at the end; they are too special, but they serve as illustration).{{each_element(Iterable $x)}}This function visits each container and leaf in the tree $x and calls a given block with 1.3 parameters. The block gets container, index, and value if defining three parameters, if using 2 arguments the container and index is delivered as a tuple, and if using 1 arg the three args are delivered as a Triple. The first yielded value is the given argument value. Each element in the tree is yielded with parent before children, depth first.When not given a block, each_element produces an Iterator that yields a triplet.{{each_container(Iterable $x)}}This function is he same as to each_element but skips children that are not containers. This enables doing inner loops conditionally.What we should do instead is to first implement {{next()}} since that makes it possible to do general skipping and pruning; {{next(true)}} means skip this element and its children and {{next()}}, or {{next(false)}} to mean "do not prune", take next element I am done with the one you just gave me.ProposalImplement flat_each such that:* It accepts an Iterable and a required block* It produces an Iterator if not given a block* When given a block, it produces the given first argument* It yields 1-3 arguments as described for each_element* The value produced by the block is ignored (as for a regular each)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.Implement flat_reduce such that:* It accepts an Any and a required block* if value is not Iterable, the given value is yielded and nothing more, else every value in the iterable is yielded to the block* It produces an Iterator if not given a block* When given a block, it produces a result that is determined by the block** For each given container* It yields up to 6 arguments, exact rules t.b.d (see below)* The value produced by the block represents the next state (see below)* If next is called, the value given to next determines if iteration continues with the next in order {{next(false)}}/{{next()}}, or if it prunes {{next(true)}}.* In contrast to the existing {{reduce}} the {{flat_reduce}} does not take an optional starting value, as that is controlled via the $direction.Example:{code:puppet}$a_tree.flat_reduce |$tree, $level, $direction, $container, $key, $val | { ... }$tree is th
Jira (PUP-7155) PCore resource output improperly quoted
Title: Message Title Henrik Lindberg commented on PUP-7155 Re: PCore resource output improperly quoted Josh Cooper We are saying the same thing. PSON is the odd format here - it is really text in an undefined encoding My statement was not very precise - should have said something like: "Given that we have specified puppet source and yaml/json/hocon/eyaml (current list of supported textual formats) inputs, and output from puppet in same formats (source, yaml, json,...) as being UTF-8, this is not a problem" - i.e. since encoding is known/the-same the bytes making up the characters can stay as they are. 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-7611) Can't turn off deprecation warnings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7611 Can't turn off deprecation warnings Change By: Josh Cooper Fix Version/s: PUP 5.0.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-7611) Can't turn off deprecation warnings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7611 Can't turn off deprecation warnings Change By: Josh Cooper Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y 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-7615) puppet command leaks module command issues.
Title: Message Title Josh Cooper commented on PUP-7615 Re: puppet command leaks module command issues. Merged to master at https://github.com/puppetlabs/puppet/commit/281b8905480ff7368237b90e646cc4428d1bb054. Adam Buxton it would be great if you could give this a try. 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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3042 If a catalog has a dependency cycle, it does not count as failed Change By: Josh Cooper Sprint: Puppet 5 Race to the Finish! Agent 2017-06-14 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-7615) puppet command leaks module command issues.
Title: Message Title Adam Buxton commented on PUP-7615 Re: puppet command leaks module command issues. Josh Cooper I'm with a client this week, is there a easy way for me to test this ? Do we have an overnight build running I can log into or can pull and vagrant run Happy to test, equally pretty happy you all know more about this fix working than I do 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-6994) acceptance: no_exception_in_reduce_with_bignum doesn't test anything
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6994 acceptance: no_exception_in_reduce_with_bignum doesn't test anything Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate 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-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title Josh Cooper commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys I haven't been paying close attention to this, but I have to say the behavior is surprising to me. I would expect an integer key to be interpreted as an index only if the parent type is a hash/array, e.g. $ puppet lookup network.interfaces.0.ipaddress vs $ puppet lookup webserver.port.80.site Alternatively, can we use brackets to make the index case explicit, like jq does: $ puppet lookup network.interfaces[0]ipaddress That way there's no ambiguity between an index and an integer key, and the user doesn't have to go through contortions to quote the integer key. Add Comment
Jira (PUP-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Nick Walker created an issue Puppet / PUP-7629 Hieradata should be loaded and cached in accordance with the environment_timeout Issue Type: Bug Assignee: Unassigned Created: 2017/06/07 11:22 AM Priority: Normal Reporter: Nick Walker The Problem When setting environment_timeout to unlimited there is an expectation that all code and hieradata be loaded into memory and not re-read from disk until the environment cache is flushed. If you change a puppet manifest on disk after it has been loaded into the puppet master the puppet master will not read that manifest. However, if you change a hiera data file on disk after it has been loaded by the puppet master it will still be reread on disk and immediately affect catalog compilation. Suggested Solution These two things are not congruent. Either all files in the $codedir should be cached until the environment cache is flush or none of the files should be cached. Performance Benefit There is presumably a performance benefit to be had from loading hieradata once and then never having to recheck files on disk until the cache is flushed.
Jira (PUP-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Nick Walker commented on PUP-7629 Re: Hieradata should be loaded and cached in accordance with the environment_timeout Henrik Lindberg Thomas Hallgren as a followup to our discussion yesterday. 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Nick Walker updated an issue Puppet / PUP-7629 Hieradata should be loaded and cached in accordance with the environment_timeout Change By: Nick Walker h1. The ProblemWhen setting environment_timeout to unlimited there is an expectation that all code and hieradata be loaded into memory and not re-read from disk until the environment cache is flushed. If you change a puppet manifest on disk after it has been loaded into the puppet master the puppet master will not read that manifest. However, if you change a hiera data file on disk after it has been loaded by the puppet master it will still be reread on re-read from disk and immediately affect catalog compilation. h1. Suggested Solution These two things are not congruent. Either all files in the $codedir should be cached until the environment cache is flush or none of the files should be cached. h1. Performance BenefitThere is presumably a performance benefit to be had from loading hieradata once and then never having to recheck files on disk until the cache is flushed. 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-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Moses Mendoza commented on PUP-1890 Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings Note - a separate PR is needed for master so leaving this in-progress 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-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Moses Mendoza commented on PUP-1890 Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings merged to puppet/stable at https://github.com/puppetlabs/puppet/commit/cab727367bbf155c638704fd94496ac655f3392c 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-1619) Memory fact fails on Solaris SPARC 11.3 patch level 17.0.3.0
Title: Message Title Stan Duffy assigned an issue to Maggie Dreyer Facter / FACT-1619 Memory fact fails on Solaris SPARC 11.3 patch level 17.0.3.0 Change By: Stan Duffy Assignee: Stan Duffy 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-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title John Duarte assigned an issue to Thomas Hallgren Puppet / PUP-7612 It is impossible to navigate an integer keyed Hiera hash using dotted keys Change By: John Duarte Assignee: John Duarte 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-7612) It is impossible to navigate an integer keyed Hiera hash using dotted keys
Title: Message Title John Duarte commented on PUP-7612 Re: It is impossible to navigate an integer keyed Hiera hash using dotted keys I am putting this issue in a 'Needs Information' status while the discussion about expected behavior is being finalized. 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-3548) travis: take more explicit control; use jobs; don't use language
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3548 travis: take more explicit control; use jobs; don't use language Change By: Rob Browning Assignee: Rob Browning 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-3548) travis: take more explicit control; use jobs; don't use language
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3548 travis: take more explicit control; use jobs; don't use language Issue Type: Improvement Assignee: Unassigned Created: 2017/06/07 12:52 PM Priority: Normal Reporter: Rob Browning Switch to a "c" project to prevent travis from trying to be helpful with respect to clojure all the time, even when we're running ruby-only tests. This should speed up our tests, and eliminate confusing issues that we've had to work around in the past. The default travis environment already has the jdks, lein, and the ruby environments that we need. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Eric Sorenson commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Today, any request to access either of the mount points would be denied. For Puppet 5, would you think the behavior should implicitly change to act like allow * instead? Assuming we're eventually intending to eliminate all use of the auth directives from the fileserver.conf file, I think this would make sense – although it could arguably be construed as a security issue if access to some mount points that had not previously been denied by auth.conf rules at a higher level started to be granted to all users after upgrading to Puppet 5. I agree with this sentiment - If no directives are there, allow. Isn't this exactly what we want users to do? We're trying to get them to stop defining access control in this file and only use it to define mount points. So why would we penalize people who do 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 (PDB-3470) Postgres sandbox for unit / integration tests
Title: Message Title Rob Browning commented on PDB-3470 Re: Postgres sandbox for unit / integration tests This work has been mostly finished, but it has been shelved because it proved impossible in the near term to obtain the changes to the jenkins workers that this would require (i.e. availability of a postgresql install or the ability to install it ourselves). Instead, we've just moved all the work to travis, where we have the necessary control. 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-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Paul Schaffer moved an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Paul Schaffer Affects Version/s: PE 2017.1.1 Affects Version/s: PUP 4.7.0 Affects Version/s: PUP 4.9.4 Key: PE PUP - 20411 7630 Project: Puppet Enterprise [Internal] 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
Jira (PDB-3541) Fix shutdown hang on on flush-and-exit (at least for db ver check)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3541 Fix shutdown hang on on flush-and-exit (at least for db ver check) Change By: Rob Browning Release Notes Summary: (Might belong alongside the documentation of the postgresql 9.6 requirement.)PuppetDB should now shut down with a non-zero exit status when it detects an unsupported PostgreSQL version. Previously it might hang while trying to exit. Release Notes: Bug Fix 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-3541) Fix shutdown hang on on flush-and-exit (at least for db ver check)
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3541 Fix shutdown hang on on flush-and-exit (at least for db ver check) Change By: Rob Browning Fix Version/s: PDB 5.0.0 Fix Version/s: PDB 4.4.1 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-3173) Add batch limit to admin endpoint node-purge command
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3173 Add batch limit to admin endpoint node-purge command Change By: Rob Browning Release Notes Summary: See PDB-3546 instead. Release Notes: Not Needed 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-3546) Add docs for node-purge-gc-batch-limit, etc.
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3546 Add docs for node-purge-gc-batch-limit, etc. Change By: Rob Browning Assignee: Rob Browning 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-3546) Add docs for node-purge-gc-batch-limit, etc.
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3546 Add docs for node-purge-gc-batch-limit, etc. Change By: Rob Browning Fix Version/s: PDB 5.0.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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Josh Cooper commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Merged to master in https://github.com/puppetlabs/puppet/commit/233975d6d326de08fbfc638374228279f6857801 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-3940) Puppet requests should include "real" MIME types
Title: Message Title Ethan Brown commented on PUP-3940 Re: Puppet requests should include "real" MIME types Merged to master in https://github.com/puppetlabs/puppet/commit/7937f7ee8a92496ac0d8db3e31e7beb033217cd7 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-7620) Add a `unique` function that works with all kinds of iterables
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7620 Add a `unique` function that works with all kinds of iterables Change By: Jorie Tappa Release Notes: New Feature 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-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Josh Cooper Team: Agent 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-6694) Fix various type system glitches, Puppet Data type should be limited to JSON types.
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-6694 Fix various type system glitches, Puppet Data type should be limited to JSON types. Change By: Jorie Tappa Release Notes: New Feature 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-6084) Remove ability to reference Class[Name] (capital Name)
Title: Message Title
Jorie Tappa updated an issue
Puppet / PUP-6084
Remove ability to reference Class[Name] (capital Name)
Change By:
Jorie Tappa
Release Notes Summary:
The ability to use of a capital name in a {{Class[MyClass]}} reference is no longer supported has been removed and will result in an error. Such references must now be written with a lower cased name e.g. {{Class[myclass]}}.
Release Notes:
Deprecation
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-7514) reduce does not work with break()
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7514 reduce does not work with break() Change By: Jorie Tappa Release Notes: Bug Fix 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-1334) Empty clientbucket files produce errors
Title: Message Title Jean Bond updated an issue Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Jean Bond Labels: redmine resolved-issue-added 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Thomas Hallgren commented on PUP-7629 Re: Hieradata should be loaded and cached in accordance with the environment_timeout The proposed change make sense and would remove the need for the stat that occurs on each file, once for every compile run. 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-7594) Hiera hash keys are being converted to strings recursively
Title: Message Title Jean Bond updated an issue Puppet / PUP-7594 Hiera hash keys are being converted to strings recursively Change By: Jean Bond Labels: regression resolved-issue-added 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-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Josh Cooper commented on PUP-7616 Re: Fix broken implementation of Property#change_to_s method Merged to master in https://github.com/puppetlabs/puppet/commit/b8f5a230e718f8679c416758c549f89160fb2f02. 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-7605) catalog.resource() doesn't accept "main" as a title parameter
Title: Message Title Josh Cooper commented on PUP-7605 Re: catalog.resource() doesn't accept "main" as a title parameter Thomas Hallgren I'm ok reopening this for more investigation and a fix down the road, if only to help define the type and provider API, but I think it's a much lower priority right now. I think we do have additional work to do in the puppetdb terminus because it is mixing data from different catalog representations, the serialized to_data_hash and Puppet::Resource::Catalog versions. 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-7628) Cannot run puppet commands or startup master when environment directory missing
Title: Message Title Dylan Ratcliffe commented on PUP-7628 Re: Cannot run puppet commands or startup master when environment directory missing Henrik Lindberg I figure you might know, was there a decision made on this behaviour in the past? Surely it has come up before 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-3231) A query in Everett is using too much cpu
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3231 A query in Everett is using too much cpu Change By: Kenn Hussey Fix Version/s: PE 2016.5.z 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-3035) PDB should use gzip when replicating data
Title: Message Title Kenn Hussey commented on PDB-3035 Re: PDB should use gzip when replicating data Russell Mull the affects version for this issue isn't appropriate; which version of PDB (not PE) applies 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Nick Walker updated an issue Puppet / PUP-7629 Hieradata should be loaded and cached in accordance with the environment_timeout Change By: Nick Walker Method Found: Needs Assessment Manual Test 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-3035) PDB should use gzip when replicating data
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3035 PDB should use gzip when replicating data Change By: Russell Mull Affects Version/s: PE Next 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-3035) PDB should use gzip when replicating data
Title: Message Title Russell Mull commented on PDB-3035 Re: PDB should use gzip when replicating data It never affected any version of anything, in the end. Updated. 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Ethan Brown Labels: win windows 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Ethan Brown Fix Version/s: PUP 4.10.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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Ethan Brown Labels: win 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Ethan Brown Fix Version/s: PUP 5.0.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-6944) Reduce the windows spec matrix
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-6944
Reduce the windows spec matrix
Change By:
Maggie Dreyer
We're currently testing puppet specs on win2008r2 and 2012r2 on 4 versions of windows as:(1) 2008 - ruby -2.3.1.1-x64 ( 4) 2012 - ruby- 2.1.9 and .1-{x86,x64}, ruby- 2.3.1 .1-{ x86 & , x64 }(2 ) 2012-ja - ruby-2 . Each combination takes ~25 mins 3.1.1-x64 , and if there are concurrent commits to LTS ruby - 2. 1. 7 9.1-x86We've recently added 2008 capacity , stable and master so we could increase that , then jobs will contend while perhaps decreasing the number of 2012 combinations.We might also want to think about adding 2.3.1 while we're here, or at least planning for coordinators it . In QENG-4408 Also, we 've talked about removing dropping ruby x86 support on Windows x64, so that would decrease the 2012 combinations matrix even more . This ticket is to implement that change in ci-job-configs /cc [~ethan], [~moses], [~glenn . sarti], [~geoff.nichols]
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-7260) Remove puppet inspect and stop honoring the audit metaparameter
Title: Message Title Moses Mendoza commented on PUP-7260 Re: Remove puppet inspect and stop honoring the audit metaparameter merged to master at https://github.com/puppetlabs/puppet/commit/572aaf41ba3cad1b14a4477aeab97e6080a27d07 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-7260) Remove puppet inspect and stop honoring the audit metaparameter
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-7260 Remove puppet inspect and stop honoring the audit metaparameter Change By: Moses Mendoza Assignee: Branan Riley 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Ethan Brown Story Points: 1 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Ethan Brown Sprint: Agent 2017-06-14 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Ethan Brown assigned an issue to Moses Mendoza Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Ethan Brown Assignee: Moses Mendoza 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Moses Mendoza commented on PUP-7627 Re: CreateSymbolicLinkW returns the wrong data type merged to stable at https://github.com/puppetlabs/puppet/commit/97f59f547df21a50dc69d90140f9a740a2b6ba69 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Moses Mendoza commented on PUP-7627 Re: CreateSymbolicLinkW returns the wrong data type merged to master at f2aa573b887a93fb309c8db039b0914db85187fe 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-1890) URI.unescape mangles UTF-8 paths producing invalid ASCII strings
Title: Message Title Moses Mendoza commented on PUP-1890 Re: URI.unescape mangles UTF-8 paths producing invalid ASCII strings master changes (remove Puppet::Indirector::Request#escaped_key and add tests for facts with spaces) merge to master at https://github.com/puppetlabs/puppet/commit/71434e99ec8a58548f561b7170b4525c210976e9. 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-7631) Acceptance failure on unquoted resource change values
Title: Message Title Moses Mendoza created an issue Puppet / PUP-7631 Acceptance failure on unquoted resource change values Issue Type: CI Blocker Assignee: Unassigned Created: 2017/06/07 5:56 PM Priority: Normal Reporter: Moses Mendoza Failure on puppet/master: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet_intn-van-sys_master/337/SLAVE_LABEL=beaker,TEST_TARGET=redhat7-64m-redhat6-64a,UNEEDED=UNEEDED/testReport/junit/(root)/tests_resource_package/yum_rb/ Expected /Package[guid]\/ensure:\ change\ from\ purged\ to\ 1\.1\ failed/ to match "redhat6-64-1: \e[1;31mError: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install guid-1.1' returned 1: Error: Nothing to do\e[0m\n\e[1;31mError: /Stage[main]/Main/Package[guid]/ensure: change from 'purged' to '1.1' failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install guid-1.1' returned 1: Error: Nothing to do\e[0m\n". Difference appears to be quoted vs unquoted values. Add Comment
Jira (PUP-7631) Acceptance failure on unquoted resource change values
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7631 Acceptance failure on unquoted resource change values Change By: Moses Mendoza Story Points: 1 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-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Moses Mendoza commented on PUP-7616 Re: Fix broken implementation of Property#change_to_s method Failure on puppet/master: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet_intn-van-sys_master/337/SLAVE_LABEL=beaker,TEST_TARGET=redhat7-64m-redhat6-64a,UNEEDED=UNEEDED/testReport/junit/(root)/tests_resource_package/yum_rb/ Expected /Package[guid]\/ensure:\ change\ from\ purged\ to\ 1\.1\ failed/ to match "redhat6-64-1: \e[1;31mError: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install guid-1.1' returned 1: Error: Nothing to do\e[0m\n\e[1;31mError: /Stage[main]/Main/Package[guid]/ensure: change from 'purged' to '1.1' failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install guid-1.1' returned 1: Error: Nothing to do\e[0m\n". Difference appears to be quoted vs unquoted values. 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-7616) Fix broken implementation of Property#change_to_s method
Title: Message Title Moses Mendoza assigned an issue to Thomas Hallgren Puppet / PUP-7616 Fix broken implementation of Property#change_to_s method Change By: Moses Mendoza Assignee: Josh Cooper 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-7627) CreateSymbolicLinkW returns the wrong data type
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7627 CreateSymbolicLinkW returns the wrong data type Change By: Geoff Nichols Team: Agent 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7629 Hieradata should be loaded and cached in accordance with the environment_timeout Change By: Henrik Lindberg Sub-team: Language 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-7629) Hieradata should be loaded and cached in accordance with the environment_timeout
Title: Message Title Henrik Lindberg commented on PUP-7629 Re: Hieradata should be loaded and cached in accordance with the environment_timeout Nick Walker and other watchers - how important is it to fix this? Should we try to get this into Puppet 5.0.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.
