Jira (FACT-1349) testing custom fact via RUBYLIB causes segfaults
Title: Message Title Peter Huene commented on FACT-1349 Re: testing custom fact via RUBYLIB causes segfaults Does it occur with passing -p to facter? It appears that Facter isn't guarding itself against facts that require puppet without using -p. It could do so by adding libfacter.so to $LOADED_FEATURES so that when Puppet attempts to require facter through facter.rb, nothing happens. Thus, this is still an issue (probably also the cause for the previous segfault, although uninitialization may have changed such that the crash no longer reproduces). 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-1349) testing custom fact via RUBYLIB causes segfaults
Title: Message Title Peter Huene commented on FACT-1349 Re: testing custom fact via RUBYLIB causes segfaults Unfortunately this is the first I've heard of this issue; not sure why this ticket was never triaged. It appeared to have crashed upon shutting down the Ruby VM and off the top of my head I can't name a reason why a trailing backslash would affect that. I'd have to test it on a recent version of facter to see if this is still an issue. 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 (NPUP-51) Implement the return statement
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-51 Implement the return statement Issue Type: New Feature Assignee: Peter Huene Created: 2017/03/21 12:19 PM Priority: Normal Reporter: Peter Huene Implement the return statement in the parser. Implement the return statement in the _expression_ evaluator (without exception handling). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (NPUP-50) Implement the next statement
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-50 Implement the next statement Issue Type: New Feature Assignee: Peter Huene Created: 2017/03/21 12:16 PM Priority: Normal Reporter: Peter Huene Implement the next statement in the parser Implement the next statement in the evaluator (without using exception handling). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (NPUP-49) Implement the break statement
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-49 Implement the break statement Issue Type: Bug Assignee: Peter Huene Created: 2017/03/21 12:10 PM Priority: Normal Reporter: Peter Huene Implement the break statement in the parser. Implement the break statement in the _expression_ evaluator without using exception handling. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (NPUP-49) Implement the break statement
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-49 Implement the break statement Change By: Peter Huene 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 (NPUP-49) Implement the break statement
Title: Message Title Peter Huene assigned an issue to Unassigned Native Puppet / NPUP-49 Implement the break statement Change By: Peter Huene Assignee: Peter Huene 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-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Peter Huene commented on PUP-6040 Re: "puppet facts" outputs indirector object instead of simple fact list Agreed with Michael; the dotted notation seems like the right approach for flat output. 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-6494) exec resources leak the command string when execution fails
Title: Message Title Peter Huene assigned an issue to qa Puppet / PUP-6494 exec resources leak the command string when execution fails Change By: Peter Huene 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-6494) exec resources leak the command string when execution fails
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet / PUP-6494 exec resources leak the command string when execution fails Change By: Peter Huene Assignee: Peter Huene 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-6494) exec resources leak the command string when execution fails
Title: Message Title Peter Huene updated an issue Puppet / PUP-6494 exec resources leak the command string when execution fails Change By: Peter Huene 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 (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title Peter Huene commented on FACT-1016 Re: Repeated resolution of a facter fact causes never GC'd object references Hi Rick Renshaw. If this is for tests that is repeatedly evaluating Facter.add calls or something along those lines, calling Facter.clear in an after hook should help: e.g.: describe Foo do after(:each) do Facter.clear end end Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6831) Change reverse.each
Title: Message Title Peter Huene commented on PUP-6831 Re: Change reverse.each No, this was incorrectly typed during creation. 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Peter Huene commented on FACT-1538 Re: Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't Also, in retrospect this is probably the wrong behavior; Facter should either have a separate "primary" ipv6 interface or just treat the ipaddress6 fact as the first non-local address it finds on any interface, like Facter 2 did. Right now if a resolver doesn't find a primary interface, the fallback logic is to use the first interface with a non-local ipv4 or ipv6 address, which means it is possible for either one of ipaddress or ipaddress6 to be link-local provided the other is not. The Windows resolver does attempt to name the primary interface and follows the same logic: https://github.com/puppetlabs/facter/blob/master/lib/src/facts/windows/networking_resolver.cc#L201 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-1538) Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't
Title: Message Title Peter Huene commented on FACT-1538 Re: Facter 3 ipaddress6 fact returns link local addresses, but Facter 2 didn't What's the full networking fact show? Facter 3's ipaddress6 is for the "primary" interface; perhaps ipaddress is non-local and caused that interface to be treated as primary? We should probably be stripping the scope id. 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-124) JSON: Inconsistent naming of function parameters
Title: Message Title Peter Huene commented on PDOC-124 Re: JSON: Inconsistent naming of function parameters The intention of the signature is to appear as if the user made a declaration in the Puppet language for the function; thus it should always use Puppet syntax rules (block parameter aside). The tag's name, however, is just data; we can include a $ for consistency if we want, or not if you consider it not really part of the "name" but just a way for the language to denote that it is a variable. 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-124) JSON: Inconsistent naming of function parameters
Title: Message Title Peter Huene commented on PDOC-124 Re: JSON: Inconsistent naming of function parameters I think it belongs in the signature as that's just something that should be displayed without processing to the user. If we strip the special characters from the name in the tag, then we should have a "is_block" and "is_vararg" attribute to convey that information instead. 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-120) Generated _index.html page is not accessible on github.io
Title: Message Title Peter Huene commented on PDOC-120 Re: Generated _index.html page is not accessible on github.io _index.html comes essentially hardcoded into a base YARD template; afaik it would require a lot of work to change its name. Our best option is probably a .nojekyll or some other configuration to have it serve the file (ideally having YARD do this automatically...or use a different file name). 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-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title Peter Huene commented on PDOC-126 Re: Ruby quoting constructs are incompletely stripped from some docstrings Yes on stripping %Q and %q (and the brackets). Yes on treating interpolated expressions as simply raw docstring text; I think it's a much better alternative than failing, although maybe generating a warning if the AST has an interpolation _expression_ in it would be ideal. 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-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title Peter Huene commented on PDOC-126 Re: Ruby quoting constructs are incompletely stripped from some docstrings 👍 thanks for the tests, looks like the quoted heredoc is operating correctly with respect to the best puppet-strings can 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 (PDOC-124) JSON: Inconsistent naming of function parameters
Title: Message Title Peter Huene commented on PDOC-124 Re: JSON: Inconsistent naming of function parameters Taking PDOC-125 into account (i.e. the decision to not tie so closely to YARD with this format), I think we could do better here by having puppet-strings remove the * and set a "is_vararg" to true, or some such. 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-125) JSON: Splitting function signatures into two places is awkward
Title: Message Title Peter Huene commented on PDOC-125 Re: JSON: Splitting function signatures into two places is awkward I'm completely fine with having a better structure that isn't tied closely to YARD, but I'd still argue that an overload's signature belongs with the overload's data (doc text, tags, etc.) because most of the time you want this displayed as a single entity in a list of overloads. 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-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title Peter Huene commented on PDOC-126 Re: Ruby quoting constructs are incompletely stripped from some docstrings I believe it would be treated the same as a double quoted string with interpolations: namely the result should contain the interpolation _expression_ as text. We should test this, William Hopper. 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-128) What's the deal with @example tags?
Title: Message Title Peter Huene commented on PDOC-128 Re: What's the deal with @example tags? It is; YARD parses the docstring and expects indentation to separate a tag's docstring from the next tag. 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-127) Hanging indent isn't stripped for resource feature descriptions
Title: Message Title Peter Huene commented on PDOC-127 Re: Hanging indent isn't stripped for resource feature descriptions Sounds like a Puppet::Util::Docs.scrub call is probably missing for features. 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-126) Ruby quoting constructs are incompletely stripped from some docstrings
Title: Message Title
Peter Huene commented on PDOC-126
Re: Ruby quoting constructs are incompletely stripped from some docstrings
Currently only string literals and heredoc expressions are supported, with the latter having known issues due to long standing "it's not a bug!" bug in YARD that we try to work around.
I think we can attempt to fix this by simply stripping both %q} and {{%Q from around the strings, although we should error if the latter attempts interpolation as that cannot be supported.
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-125) JSON: Splitting function signatures into two places is awkward
Title: Message Title Peter Huene commented on PDOC-125 Re: JSON: Splitting function signatures into two places is awkward This is funky because this is how YARD represents the data. That is to say the intention of this schema was to enable any users familiar with YARD to consume the data for their uses and not solely as a mechanism for which Puppet's doc team can generate documentation. Function objects only have a single signature, which is omitted when the function has overloads because the overload tags themselves store their signature representation. Perhaps this is not the best way of representing it, but it's consistent with how YARD does it. 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-124) JSON: Inconsistent naming of function parameters
Title: Message Title
Peter Huene commented on PDOC-124
Re: JSON: Inconsistent naming of function parameters
The name of the parameter includes the leading * to indicate it is vararg, which is not something that YARD represents outside of the parameter name (i.e. there's no "is parameter vararg" attribute on a param tag). However, the param tag's name attribute should not include a leading {{$}.
Note that the JSON schema was not designed solely for our internal docs team's use; it is simply a JSON representation of how YARD would represent things. Thus it was expected that the docs team would have to tailor this generic data for their use, rather than make the data conform to what they solely need.
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 Peter Huene commented on PDOC-60 Re: Strings skips docs for the log message functions The Ruby function handler limits its detection to "namespace only" calls, which is why it won't see a call inside of a method. Users don't generally (if ever) dynamically generate functions, so there's probably a perf benefit for being "namespace only" (at least one would hope so given that it could skip over parsing method bodies entirely). When I originally mentioned the logging functions to Nick, we thought perhaps we'd have a special way of documenting dynamically generated functions (sort of like the directives we have for metaprogrammed resource type parameters/properties); alternatively, actually having separate definitions for these functions would enable us to document them differently (without an unsupported string interpolation) and make them easier to find in Puppet's source base. The latter I would advocate for. 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-5951) Write a tool that transforms a Provider into a Pcore representation
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet / PUP-5951 Write a tool that transforms a Provider into a Pcore representation Change By: Peter Huene Assignee: Peter Huene 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-77) Create an easy way to modify the rake task to include/exclude certain files/folders.
Title: Message Title Peter Huene commented on PDOC-77 Re: Create an easy way to modify the rake task to include/exclude certain files/folders. The strings:generate task is itself a simple wrapper of PuppetStrings.generate (https://github.com/peterhuene/puppet-strings/blob/678c04957d59b297085e2bc6a422801a174a94a7/lib/puppet-strings/tasks/generate.rb), so my recommendation would be to write one's own rake task that passes the desired arguments into PuppetStrings.generate. If that is insufficient, we could add the proposed wrapper here, but I do feel that generate is already a simple enough API to wrap with one's own rake task if desired. 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-77) Create an easy way to modify the rake task to include/exclude certain files/folders.
Title: Message Title Peter Huene commented on PDOC-77 Re: Create an easy way to modify the rake task to include/exclude certain files/folders. With the new generate task, you should be able to do this: rake strings:generate\["site/**/*.pp modules/custom/**/*.rb modules/custom/**/*.pp"] That would filter to only parse Puppet source under site/, and Ruby and Puppet source under modules/custom/. No need to write a custom task or any Ruby code. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-86) Make Markdown the default format
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet Strings / PDOC-86 Make Markdown the default format Change By: Peter Huene Assignee: Peter Huene 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-6653) Ruby types still loaded even when a PCore type is found
Title: Message Title Peter Huene updated an issue Puppet / PUP-6653 Ruby types still loaded even when a PCore type is found Change By: Peter Huene Story Points: 2 Sprint: Language 2016-09-07 Scrum Team: Language Fix Version/s: PUP 4.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5950) Define how providers are represented in PCore
Title: Message Title Peter Huene commented on PUP-5950 Re: Define how providers are represented in PCore I don't believe there is. There may be some use to validating the provider attribute during compilation, but the master should avoid loading providers; that would limit us to simply looking and found provider file names, but it should be sufficient for at least building a set of names. However, it would complicate the "up-to-date" logic that puppet generate is doing now for a type, as simply installing a new module or gem that adds a provider for an existing type would invalidate it. I don't think it's worth doing at this point unless there is a need. Should I close this out "won't fix" or punt the ticket to the backlog for a future look? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-63) Blizzard of errors and warnings when run against core code
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet Strings / PDOC-63 Blizzard of errors and warnings when run against core code Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-79) [SPIKE] Define the set of tickets needed to get strings working for docs needs
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet Strings / PDOC-79 [SPIKE] Define the set of tickets needed to get strings working for docs needs Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5950) Define how providers are represented in PCore
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-5950 Define how providers are represented in PCore Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1482) mountpoints fact does not show mounts on tmpfs
Title: Message Title Peter Huene updated an issue Facter / FACT-1482 mountpoints fact does not show mounts on tmpfs Change By: Peter Huene Story Points: 1 Sprint: Client Triage Fix Version/s: FACT 3.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1482) mountpoints fact does not show mounts on tmpfs
Title: Message Title Peter Huene commented on FACT-1482 Re: mountpoints fact does not show mounts on tmpfs It's been a while, but I believe the check to filter out non-device mounts from mountpoints was to prevent lookup of partition data for mountpoints that don't map to physical device. It looks like the check was done in the wrong place, namely it should be when collecting the partition data and not when filtering the mountpoints themselves. I believe this should be addressed by moving this check https://github.com/puppetlabs/facter/blob/master/lib/src/facts/linux/filesystem_resolver.cc#L79-L82 to https://github.com/puppetlabs/facter/blob/master/lib/src/facts/linux/filesystem_resolver.cc#L140, prior to inserting the entry in the map. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6500) Investigate end to end workflow of puppet generate with code manager and r10k
Title: Message Title Peter Huene commented on PUP-6500 Re: Investigate end to end workflow of puppet generate with code manager and r10k Zachary Smith with respect to my issue #2 above, is there some context such as an environment variable or another mechanism our tool could key off of to determine the environment being deployed? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6500) Investigate end to end workflow of puppet generate with code manager and r10k
Title: Message Title Peter Huene commented on PUP-6500 Re: Investigate end to end workflow of puppet generate with code manager and r10k I was able to successfully hook in our generate tool by editing /opt/puppetlabs/server/data/code-manager/r10k.yaml to include this line: postrun: ["/usr/local/bin/puppet", "generate", "types", "--environment=production", "--environmentpath=/etc/puppetlabs/code-staging/environments"] and then triggering a deploy with puppet-code deploy production --wait. I used a nearly default template for the branch at: https://github.com/peterhuene/code-manager-test I verified that the modules with types have a pcore subdirectory in them (note: the output of the tool is out-of-date with respect to latest design decisions) and the output of the tool is correct. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6500) Investigate end to end workflow of puppet generate with code manager and r10k
Title: Message Title Peter Huene commented on PUP-6500 Re: Investigate end to end workflow of puppet generate with code manager and r10k Hi Zachary Smith. Thanks for the information. Could you elaborate on what would be required for method #3? I've set up a PE environment with code manager enabled and our "puppet generate" tool that will emit puppet code for resource types in an environment, so the next step for me is to get r10k to invoke our tool after it runs. When code manager invokes r10k, I assume it generates a config file that supersedes /etc/puppetlabs/r10k/r10k.yaml, which is why it won't respect a postrun option there? If so, could you point me at where we do this generation and perhaps I can hack something together? Many thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5948) write tool to transform ruby resource type to pcore resource type
Title: Message Title Peter Huene commented on PUP-5948 Re: write tool to transform ruby resource type to pcore resource type I'm going to mark this as ready for merge so we can review what has already been committed to https://github.com/peterhuene/puppet-generate. It needs unit tests still, but I'm waiting on the OK from product regarding the expected user story and experience for this tool. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene updated an issue Facter / FACT-1449 Facter does not honor digits as Strings Change By: Peter Huene Affects Version/s: FACT 3.1.8 Story Points: 1 Release Notes Summary: Facter treated quoted numeric and boolean values in YAML external fact files as numeric/boolean instead of respecting the quotes and treating the value as a string. Facter has been fixed to only perform the conversion for unquoted scalar values. Sprint: Client Triage Scrum Team: Client Platform Release Notes: Bug Fix Fix Version/s: FACT 3.3.0 Add Comment
Jira (FACT-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-1449 Facter does not honor digits as Strings Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene commented on FACT-1449 Re: Facter does not honor digits as Strings Found this issue on yaml-cpp: https://github.com/jbeder/yaml-cpp/issues/261 Checking to see if the tag could be used to resolve this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1449) Facter does not honor digits as Strings
Title: Message Title Peter Huene commented on FACT-1449 Re: Facter does not honor digits as Strings This is a problem in the underlying yaml-cpp library Facter uses to parse YAML. The problem is that, internally, scalar data is stored as strings, even for non-string scalars (numbers, booleans, etc). Facter attempts to use yaml-cpp's API for converting the scalar's value to a double, integer, or boolean. If the scalar data is convertible, then Facter treats the value as having that type. Thus, strings like 'true', 'false', '123', and '123.456' will all be converted to a non-string type. Given the yaml-cpp API, there is no way to prevent this from occurring other than treating all scalar values read in from a yaml file as string values. This is even less desired than the behavior described in this ticket, however. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5948) write tool to transform ruby resource type to pcore resource type
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-5948 write tool to transform ruby resource type to pcore resource type Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-48) Implement the `file` and `epp` functions.
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-48 Implement the `file` and `epp` functions. Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-48) Implement the `file` and `epp` functions.
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-48 Implement the `file` and `epp` functions. Issue Type: New Feature Affects Versions: NPUP 0.1.0 Assignee: Unassigned Created: 2016/06/28 3:21 PM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene Implement the `file` and `epp` functions in the runtime. Implement resolving of file paths based on '/' for files and templates. Add Comment
Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title Peter Huene commented on PUP-6361 Re: Validate and error if a class or define is given a name starting with :: Sorry late to the party: what about applications? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-46 Postfix call for the "type" function results in a parse error. Change By: Peter Huene Scope Change Category: Adopted Scope Change Reason: Had spare bandwidth for a very simple fix. Sprint: Language Triage 2016-06-29 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-12) Incorrect logic for detecting "value produced but forgotten" errors.
Title: Message Title Peter Huene assigned an issue to Henrik Lindberg Native Puppet / NPUP-12 Incorrect logic for detecting "value produced but forgotten" errors. Change By: Peter Huene Assignee: Peter Huene Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-9) Implement deep matches in case/selector expressions
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-9 Implement deep matches in case/selector expressions Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-12) Incorrect logic for detecting "value produced but forgotten" errors.
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-12 Incorrect logic for detecting "value produced but forgotten" errors. Change By: Peter Huene Scope Change Category: Adopted Scope Change Reason: Related to other validation work in the native parser Sprint: Language Triage 2016-06-29 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-47) Implement proper support for Unicode strings
Title: Message Title Peter Huene assigned an issue to Henrik Lindberg Native Puppet / NPUP-47 Implement proper support for Unicode strings Change By: Peter Huene Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-7) Do not allow expressions with side effects in parameter default values
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-7 Do not allow expressions with side effects in parameter default values Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-47) Implement proper support for Unicode strings
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-47 Implement proper support for Unicode strings Change By: Peter Huene Story Points: 5 3 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-47) Implement proper support for Unicode strings
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-47 Implement proper support for Unicode strings Issue Type: Bug Assignee: Peter Huene Created: 2016/06/01 12:54 PM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene Currently Unicode is, at best, somewhat supported in the Puppet language for strings. See here for a write-up about the issue. The fix is to implement a UTF-8 string type that internally uses ICU to handle Unicode graphemes. Add Comment
Jira (NPUP-44) Review the Puppet 4.0 checker and port requisite logic to validate native ASTs
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-44 Review the Puppet 4.0 checker and port requisite logic to validate native ASTs Change By: Peter Huene Sprint: Language Triage 2016-06-15 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-46
Postfix call for the "type" function results in a parse error.
Change By:
Peter Huene
The following code:{code}notice ( 1.type() ) {code}results in:{code}node 'peterhu-osx': expected name but found type keyword. notice(1.type()) ^~~~{code}This is expected to instead output:{code}Notice: Scope(Class[main]): Integer[1, 1]{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-46
Postfix call for the "type" function results in a parse error.
Change By:
Peter Huene
The following code:{code}notice 1.type () {code}results in:{code}node 'peterhu-osx': expected name but found type keyword. notice(1.type()) ^~~~{code}This is expected to instead output:{code}Notice: Scope(Class[main]): Integer[1, 1]{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-46 Postfix call for the "type" function results in a parse error. Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-46) Postfix call for the "type" function results in a parse error.
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-46 Postfix call for the "type" function results in a parse error. Issue Type: Bug Assignee: Unassigned Created: 2016/05/31 10:41 AM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene The following code: notice 1.type results in: node 'peterhu-osx': expected name but found type keyword.
Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::
Title: Message Title
Peter Huene commented on PUP-6361
Re: Validate and error if a class or define is given a name starting with ::
The native compiler validates the class name during scanning the AST for definitions (effectively a validation, although it's currently tied into the definition scanner):
class foo {
class ::bar {
}
}
Notice: compiling for node 'peterhu-osx' with environment 'production'.
Error: .../production/manifests/site.pp:2:11: node 'peterhu-osx: '::bar' is not a valid class name.
class ::bar {
^
Notice: compilation failed with 1 error and 0 warnings.
Jira (NPUP-45) Implement new function for String type
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-45 Implement new function for String type Issue Type: New Feature Assignee: Peter Huene Created: 2016/05/25 5:49 PM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene Implement the new function for the String type according to the specification. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6354) Enum entries are not unique.
Title: Message Title Peter Huene created an issue Puppet / PUP-6354 Enum entries are not unique. Issue Type: Bug Assignee: Unassigned Created: 2016/05/25 1:19 PM Fix Versions: PUP 4.5.2 Priority: Normal Reporter: Peter Huene The following code: notice Enum[foo, bar, foo, bar] produces output: Notice: Scope(Class[main]): Enum['bar', 'bar', 'foo', 'foo']
Jira (PUP-6354) Enum entries are not unique.
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6354
Enum entries are not unique.
Change By:
Peter Huene
The following code:{code}notice Enum[foo, bar, foo, bar]{code}produces output:{code}Notice: Scope(Class[main]): Enum['bar', 'bar', 'foo', 'foo']{code}Expected output:{code} notice Notice: Scope(Class[main]): Enum[ ' bar ' , ' foo ' ]{code}As the values should be in lexicographic ordering and unique.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-42) Implement new expression and function.
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-42
Implement new _expression_ and function.
Change By:
Peter Huene
Implement the "new _expression_" (function call syntax on a Type _expression_). This _expression_ should translate to calling the {{new}} function with the type as the first argument, e.g. {{Integer(...) => new(Integer, ...)}}.Implement the new function according to Puppet specifications. Note: this excludes the overload of the new function for {{String}}. That will be implemented later once unicode strings are properly implemented.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet
Title: Message Title
Peter Huene created an issue
Puppet / PUP-6347
new function (String): programmatic representation escapes for Ruby language and not Puppet
Issue Type:
Bug
Affects Versions:
PUP 4.5.0
Assignee:
Unassigned
Created:
2016/05/24 12:14 AM
Fix Versions:
PUP 4.5.2
Priority:
Normal
Reporter:
Peter Huene
Conversions to String using the new function with the %p format escapes characters for the Ruby language and not the Puppet language.
notice String('foo#{bar}', '%p')
notice String("\u{1b}", '%p')
Jira (PUP-6346) new function (String): not all string-based conversions respect width and precision
Title: Message Title Peter Huene updated an issue Puppet / PUP-6346 new function (String): not all string-based conversions respect width and precision Change By: Peter Huene Summary: String. new function (String) : not all string-based conversions respect width and precision Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6346) String.new: not all string-based conversions respect width and precision
Title: Message Title Peter Huene created an issue Puppet / PUP-6346 String.new: not all string-based conversions respect width and precision Issue Type: Bug Affects Versions: PUP 4.5.0 Assignee: Unassigned Created: 2016/05/24 12:04 AM Fix Versions: PUP 4.5.2 Priority: Normal Reporter: Peter Huene Certain conversions to String using the new function respect width and precision of the format argument while some others do not. Examples: notice String(undef, '%.1p') notice String(undef, '%#.1p')
Jira (NPUP-44) Review the Puppet 4.0 checker and port requisite logic to validate native ASTs
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-44 Review the Puppet 4.0 checker and port requisite logic to validate native ASTs Issue Type: New Feature Assignee: Peter Huene Created: 2016/05/23 3:14 PM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene Review the functionality of the 4.0 AST checker (puppet/pops/validation/checker4_0.rb) and port the requisite validations to the native parser such that the ASTs produces pass the same checks. This will enable the native parser to produce an AST that the Ruby implementation doesn't need to validate for correctness. Add Comment
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect {{Integer.new}} to be consistent with that conversion. * Note: this also affects {{Float.new}} (and by extension {{Numeric.new}}). *
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect {{Integer.new}} to be consistent with that conversion. Note: this also affects {{Float.new}} (and by extension {{Numeric.new}}).
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title Peter Huene updated an issue Puppet / PUP-6314 Integer.new does not accept whitespace between sign and leading digit Change By: Peter Huene Summary: Numeric Integer .new does not accept whitespace between sign and leading digit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6314) Numeric.new does not accept whitespace between sign and leading digit
Title: Message Title Peter Huene updated an issue Puppet / PUP-6314 Numeric.new does not accept whitespace between sign and leading digit Change By: Peter Huene Summary: Integer Numeric .new does not accept whitespace between sign and leading digit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect ` {{ Integer.new ` }} to be consistent with that conversion.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic string \ -> integer conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect `Integer.new` to be consistent with that conversion.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene created an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Issue Type:
Bug
Affects Versions:
PUP 4.5.0
Assignee:
Unassigned
Created:
2016/05/16 5:13 PM
Fix Versions:
PUP 4.5.1
Priority:
Normal
Reporter:
Peter Huene
The following Puppet code:
notice Integer.new('+ 1')
results in the following error:
Jira (PUP-6314) Integer.new does not accept whitespace between sign and leading digit
Title: Message Title
Peter Huene updated an issue
Puppet / PUP-6314
Integer.new does not accept whitespace between sign and leading digit
Change By:
Peter Huene
The following Puppet code:{code}notice Integer.new('+ 1'){code}results in the following error:{code}Error while evaluating a Function Call, invalid value for Integer(): "+ 1"{code}Expected this to print:{code}Notice: Scope(Class[main]): 1{code}The problem is the whitespace between the sign and the leading digit in the number; we support it for arithmetic string \-> integer {{String}} to {{Integer}} conversions (e.g. {{notice '+ 1' + '- 1'}} results in {{0}}), so I expect `Integer.new` to be consistent with that conversion.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1413) External facts do not override custom Ruby facts that have confines or a non-default weight
Title: Message Title Peter Huene commented on FACT-1413 Re: External facts do not override custom Ruby facts that have confines or a non-default weight Not at all. I also think the documentation should be updated to say that it needs to be >= 0. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-43) Missing a colon after a resource title causes confusing error message
Title: Message Title
Peter Huene created an issue
Native Puppet / NPUP-43
Missing a colon after a resource title causes confusing error message
Issue Type:
Bug
Affects Versions:
NPUP 0.1.0
Assignee:
Peter Huene
Created:
2016/05/10 2:04 PM
Priority:
Normal
Reporter:
Peter Huene
The following:
file {
foo
}
Results in this error message:
Jira (FACT-1413) External facts do not override custom Ruby facts that have confines or a non-default weight
Title: Message Title Peter Huene updated an issue Facter / FACT-1413 External facts do not override custom Ruby facts that have confines or a non-default weight I believe one possible solution would be: 1. Instead of resolving external facts into the facts collection, resolve them into an 'external facts' collection. 2. When evaluating custom facts, first add a resolution for each fact in the 'external facts' collection, but use a weight of 1 (the same value that Facter 2.x used). This will restore the 2.x behavior. 3. If custom facts weren't evaluated (no ruby library or --no-custom-facts), then merge the external facts collection into the output facts collection. Change By: Peter Huene Story Points: 3 Sprint: Client Triage Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6282) Confusing error message when doing a variable assignment followed by bare hash with explicitly quoted keys
Title: Message Title
Peter Huene commented on PUP-6282
Re: Confusing error message when doing a variable assignment followed by bare hash with explicitly quoted keys
I have a simple fix to improve the native compiler's error message for a resource _expression_ missing a colon:
Error: test.pp:1:12: node 'peterhu': expected ':' but found '}'.
file { foo }
^
This was solved with Spirit's ability to do a negation match on a rule without consuming a token, i.e. the resource body rule was updated to be "an _expression_ followed by something that isn't token '=>' (non-consuming) expected to be followed by token ':' expected to be followed by attributes".
Thus if the token following foo in the above example is =>, it gracefully fails to match the resource body rule (and thus the resource _expression_ rule) and continues to match other rules; however, if the token is not =>, it is expected to be :, thus failing with a better error message where previously it was falling back to matching the name rule and then the hash rule (where this is an expectation point that a => token comes after an _expression_).
Add Comment
This message was sent by Atlassian JIRA
Jira (PUP-6282) Confusing error message when doing a variable assignment followed by bare hash with explicitly quoted keys
Title: Message Title
Peter Huene commented on PUP-6282
Re: Confusing error message when doing a variable assignment followed by bare hash with explicitly quoted keys
The native parser gives this for both examples:
Notice: compiling for node 'peterhu-osx.delivery.puppetlabs.net' with environment 'production'.
Error: example.pp:6:43: node 'peterhu-osx': expected '=>' but found '}'.
}.each |$x| { notify { "${x[0]}: ${x[1]}" } }
^
Notice: compilation failed with 1 error and 0 warnings.
That is because of the missing : after the resource title, forcing the lookahead for a resource declaration to fail, failing back to assuming it is a name followed by a hash (hence the "expected a =>" bit).
Add Comment
Jira (NPUP-42) Implement new expression and function.
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-42
Implement new _expression_ and function.
Change By:
Peter Huene
Implement the "new _expression_" (function call syntax on a Type _expression_). This _expression_ should translate to calling the {{new}} function with the type as the first argument, e.g. {{ Integer(...) => new(Integer, ...)}}.Implement the new function according to Puppet specifications.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-42) Implement new expression and function.
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-42 Implement new _expression_ and function. Issue Type: Bug Assignee: Peter Huene Created: 2016/05/09 1:06 PM Fix Versions: NPUP 0.1.0 Priority: Normal Reporter: Peter Huene Implement the "new _expression_" (function call syntax on a Type _expression_). This _expression_ should translate to calling the new function with the type as the first argument, e.g. new(Integer, ...). Implement the new function according to Puppet specifications. Add Comment
Jira (NPUP-10) Implement automatic String to Numeric conversion for arithmetic operators.
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-10 Implement automatic String to Numeric conversion for arithmetic operators. Change By: Peter Huene Sprint: Language 2016-05-18 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-9) Implement deep matches in case/selector expressions
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-9 Implement deep matches in case/selector expressions Change By: Peter Huene Sprint: Language 2016-05-18 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-37) Allow functions declared in an environment to be made private
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-37 Allow functions declared in an environment to be made private Change By: Peter Huene Sprint: Language Triage 2016-05-18 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-9) Implement deep matches in case/selector expressions
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-9 Implement deep matches in case/selector expressions Change By: Peter Huene Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-7) Do not allow expressions with side effects in parameter default values
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-7 Do not allow expressions with side effects in parameter default values Change By: Peter Huene Sprint: Language Triage 2016-05-18 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-8) Implement mass assignment from Array and Hash
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-8 Implement mass assignment from Array and Hash Change By: Peter Huene Scope Change Category: Adopted Affects Version/s: NPUP 0.1.0 Scope Change Reason: Adopted due to extra bandwidth Sprint: Language 2016-05-04 Fix Version/s: NPUP 0.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe
Jira (NPUP-8) Implement mass assignment from Array and Hash
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-8 Implement mass assignment from Array and Hash Change By: Peter Huene Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-41) Implement the `type` function.
Title: Message Title Peter Huene assigned an issue to Thomas Hallgren Native Puppet / NPUP-41 Implement the `type` function. Change By: Peter Huene Assignee: Peter Huene Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-28) Integrate Onigmo for maximum regex compatibility with existing Puppet regular expressions
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-28 Integrate Onigmo for maximum regex compatibility with existing Puppet regular expressions Change By: Peter Huene Scope Change Category: Adopted Scope Change Reason: Adopted into the sprint as deemed an important feature to implement Sprint: Language Triage 2016-05-04 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
