Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Nicholas Fagerlund Would you say it is the "class as resource" that does it wrong, or was that only used to illustrate and the problem is much wider? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Replacing the resource like instantiations with include makes the examples work. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Eric Thompson QA Risk Assessment Reason: existing. serious QA Highest Test Level: Acceptance QA Risk Assessment: Medium QA Risk Probability: Medium QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet
Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Henrik Lindberg Sprint: Language Triage 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Henrik Lindberg Fix Version/s: PUP 4.3.3 Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Henrik Lindberg Story Points: 2 PUP-121 was about removing relative lookup of class names, and it was marked as resolved in Puppet 3.7.0 (with future parser enabled). It was never actually resolved at all in the 3 series, although it's fixed in 4.0. This is a significant language difference, which seems to have the potential to cause problems for upgraders. The following two manifests prove that this was never resolved:{code}class foo::thing { notify {"from foo::thing":}}class thing { notify {"from ::thing":}}class foo { class {'thing':}}include foo{code}The above should notify "from ::thing," but in Puppet 3.8 it will notify "from foo::thing" instead. {code}class bar::other { class {'other':}}class other { notify {"from ::other":}}include bar::other{code}The above should compile cleanly and notify "from ::other," but in Puppet 3.8 it will fail with a duplicate declaration error.Furthermore, PUP-121 says that the tests in spec/integration/parser/future_compiler_spec.rb, under "when resolving class references" are supposed to prove this is fixed, but they actually seem to have nothing to do with the problem described in PUP-121 (i.e. "include 'thing' can include something other than the one class named 'thing'"). If we don't have any real tests that check for this misbehavior, we need some. UPDATEWe should add the tests in this ticket to 3.x and make them work for parser=future.Then merge that to stable and make the tests standard and ensure runtime works as expected - fix the issues. Then merge to master. Add Comment This message
Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Steve Barlow Fix Version/s: PUP 3.8.6 Fix Version/s: PUP 3.8.7 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Henrik Lindberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Nicholas Fagerlund commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Also, remember there's work on this ticket needed for 4.x as well: we need tests that actually test this behavior, and all existing tests appear to have nothing to do with it. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Nick, yes, thanks, and thanks for test cases - the inadequate tests are the first thing to fix. I am chalking up the omission to "it is hard to understand how dynamic scoping works in the first place, making it even harder to write tests that cover all angels" Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Verified that this is still a problem in 3.x HEAD (i.e. what will be released at 3.8.4). Ran with and without --parser=future with the same result. We should fix the --parser=future path to work as on 4.x, but leave the 3.x (non future parser) behavior as is. I have not checked if we have regressed from 3.7.0, but we may have inadequate unit tests. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg commented on PUP-4818 Re: PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Hmm, this was off my radar. I assigned to Language team, and put it in our triage sprint. I tentative assigned it to 3.8.6 (although that's not a planned release yet, so we'll see). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Fix Version/s: PUP 3.8.5 Fix Version/s: PUP 3.8.6 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Fix Version/s: PUP 3.8.4 Fix Version/s: PUP 3.8.5 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Hailee Kenney Fix Version/s: PUP 3.8.3 Fix Version/s: PUP 3.8.4 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Summary: PUP-121(relativenamespacing)wasnever acutally actually resolvedin3.xfutureparser Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Fix Version/s: PUP3.8.2 Fix Version/s: PUP3.8.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.