date:20160412

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene assigned an issue to Peter Huene 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-38 
 
 
 
  Respect `environment` scope.  
 
 
 
 
 
 
 
 
 

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-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0 instead of "infinity".  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 The following code:{code}notice(Tuple >= Tuple[String]){code}Outputs {{false}}.  This is because the {{Tuple}} on the LHS has a min/max value of 0, which makes the bounds check on the {{Tuple}} on the RHS, which has min/max of 1, evaluate to false.Based on the specification of {{Tuple}}, a default constructed {{Tuple}} should have a "positive infinity"  default max value  (i.e. max  value of  {{Integer}})  default value .  Therefore it is expected that the above code outputs {{true}} as all instances of {{Tuple}} should be assignable to default {{Tuple}}. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0 instead of "infinity".  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Summary:
 
 Default Tuple type constructed with "max" of 0  instead of "infinity". 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6167) Default Tuple type constructed with "max" of 0

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Sprint:
 
 Language  2016-05-04  Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0 instead of "infinity".  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 The following code:{code}notice(Tuple >= Tuple[String]){code}Outputs {{false}}.  This is because the {{Tuple}} on the LHS has a  ( min/max value of 0 ) , which makes the bounds check on the {{Tuple}} on the RHS  ( , which has min/max of 1 ) ,  evaluate to false.Based on the specification of {{Tuple}}, a default constructed {{Tuple}} should have a "positive infinity" (i.e. max value of {{Integer}}) default value.  Therefore it is expected that the above code outputs {{true}} as all instances of {{Tuple}} should be assignable to default {{Tuple}}. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6167) Default Tuple type constructed with "max" of 0

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 The following code:{code}notice(Tuple >= Tuple[String]){code}Outputs {{false}}.  This is because the {{Tuple}} on the LHS has a  (min/  max value of 0 ) , which makes the bounds check on the {{Tuple}} on the RHS  (which has min/max of 1)  evaluate to false.Based on the specification of {{Tuple}}, a default constructed {{Tuple}} should have a "positive infinity" (i.e. max value of {{Integer}}) default value.  Therefore it is expected that the above code outputs {{true}} as all instances of {{Tuple}} should be assignable to default {{Tuple}}. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6167) Default Tuple type constructed with "max" of 0

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.4.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/12 3:50 PM 
 
 
 

Fix Versions:
 

 PUP 4.5.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 
The following code: 
 
 
 
 
 
 
notice(Tuple >= Tuple[String])
 
 
 
 
 
 
 
Outputs false. This is because the Tuple on the LHS has a max value of 0, which makes the bounds check on the Tuple on the RHS evaluate to false. 
Based on the specification of Tuple, a default constructed Tuple should have a "positive infinity" (i.e.

Jira (PUP-5825) systemd service provider always enables service in chroot

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-5825 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: systemd service provider always enables service in chroot  
 
 
 
 
 
 
 
 
 
 
Eric Thompson the test for 

PUP-6140
 covers this code change well for regular RedHats. Unless we want to write a test that specifically sets up a chroot, I think we're covered. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1375) Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1375 
 
 
 
  Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1375) Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1375 
 
 
 
  Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Highest Test Level:
 
 Acceptance 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5825) systemd service provider always enables service in chroot

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5825 
 
 
 
  systemd service provider always enables service in chroot  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment:
 
 High 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5825) systemd service provider always enables service in chroot

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5825 
 
 
 
  systemd service provider always enables service in chroot  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Highest Test Level:
 
 Acceptance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5825) systemd service provider always enables service in chroot

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5825 
 
 
 
  systemd service provider always enables service in chroot  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Severity Reason:
 
 enabling services when not intended or unknown 
 
 
 

QA Risk Probability:
 
 Medium 
 
 
 

QA Risk Severity:
 
 High 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5825) systemd service provider always enables service in chroot

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-5825 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: systemd service provider always enables service in chroot  
 
 
 
 
 
 
 
 
 
 
William Hopper does pup-6140 cover this in acceptance? or should we have another test case for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6137) Name anonymous Object when bound to a type name.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6137 
 
 
 
  Name anonymous Object when bound to a type name.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6102) A type alias that has an alias name of a built-in type should be illegal

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6102 
 
 
 
  A type alias that has an alias name of a built-in type should be illegal  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 John Duarte qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-39) Conform to Puppet's `assignable?` logic.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-39 
 
 
 
  Conform to Puppet's `assignable?` logic.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Story Points:
 
 3 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6137) Name anonymous Object when bound to a type name.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6137 
 
 
 
  Name anonymous Object when bound to a type name.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Highest Test Level:
 
 Unit 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6137) Name anonymous Object when bound to a type name.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6137 
 
 
 
  Name anonymous Object when bound to a type name.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5616) puppet device convergence impossibility, and improved error output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-5616 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet device convergence impossibility, and improved error output  
 
 
 
 
 
 
 
 
 
 
does this need a release notes blurb? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5616) puppet device convergence impossibility, and improved error output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5616 
 
 
 
  puppet device convergence impossibility, and improved error output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5616) puppet device convergence impossibility, and improved error output

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5616 
 
 
 
  puppet device convergence impossibility, and improved error output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1389) Facter.rb regression when called from MCO

2016-04-12 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1389 
 
 
 
  Facter.rb regression when called from MCO  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Release Notes Summary:
 
 Regression wasn't released. 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1389) Facter.rb regression when called from MCO

2016-04-12 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1389 
 
 
 
  Facter.rb regression when called from MCO  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/12 1:57 PM 
 
 
 

Fix Versions:
 

 FACT 3.1.6 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
The work for 

FACT-1294
 caused a regression when running Facter from MCO (as a service), where we try to load facter.rb but Puppet Labs/facter/bin isn't on the PATH. Previously facter.rb ensured it was added to the path, but the change in 

FACT-1294
 accidentally dropped that (as part of an assumption that the next release would be with new MSI packaging that put ruby.exe and libfacter in the same directory). 
Restore setting PATH as part of loading libfacter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times

2016-04-12 Thread Glenn Sarti (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-5588 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times  
 
 
 
 
 
 
 
 
 
 
Setting up validation in Windows for Azure; 
Windows 
 

Clone the repo
 

Add the following to gemfile.local 
 
 
 
 
 
 
gem 'fuubar' 
 
 
 
 
  
 
 
 
 
if RUBY_VERSION == "1.8.7" 
 
 
 
 
  gem 'debugger' 
 
 
 
 
elsif RUBY_VERSION =~ /^2\./ 
 
 
 
 
  gem "pry-byebug" 
 
 
 
 
else 
 
 
 
 
  gem "pry-debugger"

Jira (PUP-6164) Update links.puppetlabs.com links to links.puppet.com

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-6164 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update links.puppetlabs.com links to links.puppet.com  
 
 
 
 
 
 
 
 
 
 
Don't do this until IT has established the new app. The links.puppetlabs links should all soon be redirected to the correct place for a while, until the new system is in place. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6166) Authorization Certificate Extensions

2016-04-12 Thread Reid Vandewiele (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6166 
 
 
 
  Authorization Certificate Extensions  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/12 1:27 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Reid Vandewiele 
 
 
 
 
 
 
 
 
 
 
Provide a clean mechanism for setting certificate extensions to be used for cert-based authorizations (e.g. in 

TK-293
). This mechanism needs to be different from our existing certificate extensions due to the need to prevent authorization-granting certificates from being accidentally signed. 
The logical way to do this is to create a new OID arc specifically for authorization-granting extensions. 
Our root OID is 1.3.6.1.4.1.34380 for "puppetlabs". We then have: 
 
 
 
 
 
 
puppetlabs.1:   "Puppet Certificate Extension" 
 
 
 
 
puppetlabs.1.1: "Puppet Registered Certificate Extension" (ppRegCertExt)

Jira (FACT-1387) Google Cloud instances are not recognised as virtual on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1387 
 
 
 
  Google Cloud instances are not recognised as virtual on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6120) Pip package provider doesn't honor config for custom PyPI repositories

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6120 
 
 
 
  Pip package provider doesn't honor config for custom PyPI repositories  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  FACT-1284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 
 
We could add a new function that returns what you desire (we actually already get back exactly that from our internal C++ API: exit code, stdout, stderr) so that would be trivial to do. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

2016-04-12 Thread Clay Caviness (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Clay Caviness commented on  FACT-1284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 
 
In the meantime, creating an :on_fail-like option for non-zero return would be great. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result

2016-04-12 Thread Clay Caviness (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Clay Caviness commented on  FACT-1284 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result  
 
 
 
 
 
 
 
 
 
 
Not having access to the process return code is really making us do awkward things like Facter::Core::Execution.execute("/some/binary -with -args && echo true || echo false) == "true" 
In my dreams, I wish that way back in the dawn of time, Facter::Core::Execution.execute (and the puppet equivalent}} was wrapping a popen3-style call, where I could pass in an array and get stdout, stderr, and return_code back separately. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PDB-2622) PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service

2016-04-12 Thread Nick Walker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2622 
 
 
 
  PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 h1. The ProblemWhile doing some performance testing I noticed that my disk IO was maxed out on a vacuum command.  For a while I thought it was autovacuum but then I investigated and found that it was an explicit {{vacuum ( analyze, verbose)}} that puppetdb was running.  My database is roughly 180GB at this time and I think the analyze was probably picking up a lot of pages off disk and putting them in the cache but then they weren't needed again so they were being thrown out by more often used pages.  If it was doing this on the reports table that would probably take a long time to read 120GB of data off disk.  I think it's particularly problematic that this runs at startup of the service because if you run into some issue and you tune something and restart the service now you've introduced a query that itself may cause you performance problems.  Also, if you restart the whole box that is running puppetdb and postgresql then your postgresql server will be reading pages from disk for agents running puppet and also for this vacuum process that will be competing for resources.  h1.  Suggested SolutionDon't run vacuum analyze on startup.  If we need to ensure stats are updated we should trust autovacuum to do that.  If we're worried about tables with less than 50 rows that wouldn't be hit by default autovacuum settings then we should find a way to discover those tables and only vacuum them.   We could also consider tuning autovacuum settings on these small tables to make sure that a new row would trigger an autovacuum on the small tables.  I think that'd be a combo of autovacuum_vacuum_threshold = 1 autovacuum_analyze_threshold = 1 autovacuum_vacuum_scale_factor = .01 autovacuum_analyze_scale_factor = .01 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PDB-2622) PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service

2016-04-12 Thread Nick Walker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2622 
 
 
 
  PuppetDB Should Not Run VACUUM ANALYZE on Startup of Service  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDB 4.0.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/12 11:57 AM 
 
 
 

Labels:
 

 tcse 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 
The Problem 
While doing some performance testing I noticed that my disk IO was maxed out on a vacuum command. For a while I thought it was autovacuum but then I investigated and found that it was an explicit vacuum ( analyze, verbose) that puppetdb was running.  
My database is roughly 180GB at this time and I think the analyze was probably picking up a lot of pages off disk and putting them in the cache but then they weren't needed again so they were being thrown out by more often used pages. If it was doing this on the reports table that would probably take a long time to read 120GB of data off disk.  
I think it's particularly problematic that this runs at startup of the service because if you run into some issue and you tune something and restart the service now you've introduced a query that itself may cause you performance problems. Also, if you restart the whole box that is running puppetdb and postgresql then your postgresql

Jira (PUP-6165) it should not be possible to disable manifest ordering

2016-04-12 Thread R.I.Pienaar (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R.I.Pienaar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6165 
 
 
 
  it should not be possible to disable manifest ordering  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.4.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/12 11:48 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 R.I.Pienaar 
 
 
 
 
 
 
 
 
 
 
Manifest ordering have as far as I can tell been proven to work, problem is with it being configurable it's not something one can really rely on in public code as you just have no way to know if your users have it on or not. 
When next allowed by semver I'd propose it be turned on and remain on without the option to configure. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-6160) Triage 3.x acceptance failure

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6160 
 
 
 
  Triage 3.x acceptance failure  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Story Points:
 
 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-6164) Update links.puppetlabs.com links to links.puppet.com

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6164 
 
 
 
  Update links.puppetlabs.com links to links.puppet.com  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/12 11:40 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 
This will need to be done in facter, hiera, puppet-agent, mco and possibly other projects as well. Setting this ticket in the PUP project for now, and we can just use (docs) for the commit message. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6160) Triage 3.x acceptance failure

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6160 
 
 
 
  Triage 3.x acceptance failure  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Sprint:
 
 Client 2016-04-20 (Bigga Bugs) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6160) Triage 3.x acceptance failure

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-6160 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Triage 3.x acceptance failure  
 
 
 
 
 
 
 
 
 
 
So far what I know is: this one test doesn't fail in isolation, but does fail when the whole test is run. Also I should add storypoints and pull it in the sprint, since it's taking some time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6163) Systemd / Init: Service provider inconsistently picked when querying or changing SysVinit services

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6163 
 
 
 
  Systemd / Init: Service provider inconsistently picked when querying or changing SysVinit services  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.4.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/12 11:24 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 
In EL7 (and possibly other platforms), Puppet chooses different service providers when just querying a service and when actually changing it. Example: 
 
 
 
 
 
 
[root@ebdj2qy9lc1axzg puppet]# bundle exec puppet resource service logstash --param provider 
 
 
 
 
service { 'logstash': 
 
 
 
 
  ensure   => 'stopped',

Jira (FACT-1043) Falsely reporting virtual as physical under Windows for OpenStack instance

2016-04-12 Thread Jasmine Nouriel (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jasmine Nouriel commented on  FACT-1043 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Falsely reporting virtual as physical under Windows for OpenStack instance  
 
 
 
 
 
 
 
 
 
 
Opened a pull request to fix this issue: https://github.com/puppetlabs/facter/pull/1301 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6128) QualifiedReference should retain case

2016-04-12 Thread Kurt Wall (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kurt Wall commented on  PUP-6128 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: QualifiedReference should retain case  
 
 
 
 
 
 
 
 
 
 
Seeing a possible related failure in puppet server acceptance: SERVER-1258. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3827) Errors from indirected routes don't match error schema

2016-04-12 Thread Justin Stoller (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-3827 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Errors from indirected routes don't match error schema  
 
 
 
 
 
 
 
 
 
 
I've put up a PR for this here: https://github.com/puppetlabs/puppet/pull/4875 
I initially began with an approach that would check to see if the accept headers had been set, but I quickly realized in testing that the accept headers will sometimes have to be set to "text/pson" to be a valid request to the indirector. So a valid request will sometimes not trigger the "application/json" requirement and backwards compatibility cannot be kept unless we explicitly ignore the accept header in those cases. Given that, I just made the indirected route handler as similar to other handlers as possible (no attempt to catch errors). 
We are validating a fair bit of functionality of the IndirectedRoutes class by return codes, which had to be changed to validate based on the error raised since catching errors and updating the response with return codes is now done higher up the stack. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6162) Type errors for type annotations used in v4 functions can use some user friendliness

2016-04-12 Thread Daniele Sluijters (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniele Sluijters updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6162 
 
 
 
  Type errors for type annotations used in v4 functions can use some user friendliness  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniele Sluijters 
 
 
 
 
 
 
 
 
 
 When using type annotations with the Puppet 4 function API the error messages can get a bit confusing:For example, when violating a type annotation  ({{cname}} is not allowed for {{type}}) :{code}Puppet::Functions.create_function(:'nameless::discover') do  options_type = 'Struct[{\'protocol\' => Optional[String], ' \ '\'type\' => Optional[Enum[a, srv]], ' \ '\'min_records\' => Optional[Integer]}]'  dispatch :discover doparam 'String', :serviceparam 'Array', :podsoptional_param options_type, :options  end  dispatch :discover_single_pod doparam 'String', :serviceparam 'String', :podoptional_param options_type, :options  end[...]end{code}{code}notice(nameless::discover('forgeapi', podservice::pods(), { 'type' => 'cname'})){code}You're greeted with:{noformat}Error: Evaluation Error: Error while evaluating a Function Call, function 'nameless::discover' called with mis-matched argumentsexpected one of:  nameless::discover(String service, Array[Data] pods, Struct[{'protocol'=>Optional[String], 'type'=>Optional[Enum['a', 'srv']], 'min_records'=>Optional[Integer]}] options?) - arg count {2,3}  nameless::discover(String service, String pod, Struct[{'protocol'=>Optional[String], 'type'=>Optional[Enum['a', 'srv']], 'min_records'=>Optional[Integer]}] options?) - arg count {2,3}actual:  nameless::discover(String, Tuple[String, String, String, String, String, String, String, String, String, String, String, String, String], Struct[{'type'=>String}]) - arg count {3} at /etc/puppetlabs/code/environments/production/manifests/site.pp:21:8 on node ...{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6162) Type errors for type annotations used in v4 functions can use some user friendliness

2016-04-12 Thread Daniele Sluijters (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniele Sluijters commented on  PUP-6162 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Type errors for type annotations used in v4 functions can use some user friendliness  
 
 
 
 
 
 
 
 
 
 
If you butcher the type annotation in any way you get the generic error message: 
 
 
 
 
 
 
Error: Evaluation Error: Error while evaluating a Function Call, The _expression_  Optional[String], type => Optional[Enum[a, srv]], min_records => Optional[Integer]}]> is not a valid type specification.
 
 
 
 
 
 
 
In this case type is a reserved keyword and when used in a type annotation like this must be quoted. When you add the same type annotation to a Puppet manifest you get an error message that tells you exactly this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6162) Type errors for type annotations used in v4 functions can use some user friendliness

2016-04-12 Thread Daniele Sluijters (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniele Sluijters created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6162 
 
 
 
  Type errors for type annotations used in v4 functions can use some user friendliness  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2016/04/12 9:32 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Daniele Sluijters 
 
 
 
 
 
 
 
 
 
 
When using type annotations with the Puppet 4 function API the error messages can get a bit confusing: 
For example, when violating a type annotation: 
 
 
 
 
 
 
Puppet::Functions.create_function(:'nameless::discover') do 
 
 
 
 
  options_type = 'Struct[{\'protocol\' => Optional[String], ' \ 
 
 
 
 
 '\'type\' => Optional[Enum[a, srv]], ' \

Jira (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6157 
 
 
 
  Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Fixed the issue while testing what's causing it. Might just as well submit a PR 
 
 
 

Sprint:
 
 Language 2016- 05- 04 -20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6157 
 
 
 
  Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 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 (PUP-6148) Callable#assignable? results in undefined method `assignable?' for nil:NilClass

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6148 
 
 
 
  Callable#assignable? results in undefined method `assignable?' for nil:NilClass  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6148) Callable#assignable? results in undefined method `assignable?' for nil:NilClass

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6148 
 
 
 
  Callable#assignable? results in undefined method `assignable?' for nil:NilClass  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6148) Callable#assignable? results in undefined method `assignable?' for nil:NilClass

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6148 
 
 
 
  Callable#assignable? results in undefined method `assignable?' for nil:NilClass  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6147) PStructType#assignable? ignores Hash key type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6147 
 
 
 
  PStructType#assignable? ignores Hash key type.  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6147) PStructType#assignable? ignores Hash key type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6147 
 
 
 
  PStructType#assignable? ignores Hash key type.  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6147) PStructType#assignable? ignores Hash key type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6147 
 
 
 
  PStructType#assignable? ignores Hash key type.  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6147) PStructType#assignable? ignores Hash key type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6147 
 
 
 
  PStructType#assignable? ignores Hash key type.  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 The following code:{code}notice(Struct[{foo => String,  { bar => String}] >= Hash[Integer, String, 2, 2]){code}outputs {{true}} because it ignores the key type in the {{Hash}} entirely for required keys.It is expected that this outputs {{false}} because the keys of the {{Hash}} are not strings.I would also expect a {{Hash}} with key type {{String[2]}} to not be assignable if all the keys in the structure are of length 1, for example, so the key strings in the structure probably need to be checked to see if they are an instance of the {{Hash}} key type.ACCEPTANCE CRITERIAThat the above example outputs {{false}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6146) PStructType#assignable? may return nil when compared against a Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6146 
 
 
 
  PStructType#assignable? may return nil when compared against a Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6146) PStructType#assignable? may return nil when compared against a Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6146 
 
 
 
  PStructType#assignable? may return nil when compared against a Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6146) PStructType#assignable? may return nil when compared against a Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6146 
 
 
 
  PStructType#assignable? may return nil when compared against a Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6161) puppet failes during OSX RTC wakups

2016-04-12 Thread Michael Krause (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Krause created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6161 
 
 
 
  puppet failes during OSX RTC wakups  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.6 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2016/04/12 8:40 AM 
 
 
 

Environment:
 
 
OS: MacOS 10.9 to 10.11 
 
 
 

Labels:
 

 osx client bug 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michael Krause 
 
 
 
 
 
 
 
 
 
 
There are several issues with the puppet service generating error reports when it is being run during the very short uptime cycle when some of our Macs wake up from sleep to re-register their services with ARP Proxy devices on the network [ Wake reason: RTC (Alarm) ]. 
Example Log: https://gist.github.com/octomike/be9b76d0dc164c41c84bd7fffa97e916

Jira (PUP-6145) Stack overflow when checking assignability of recursive aliases

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6145 
 
 
 
  Stack overflow when checking assignability of recursive aliases  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6145) Stack overflow when checking assignability of recursive aliases

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6145 
 
 
 
  Stack overflow when checking assignability of recursive aliases  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6145) Stack overflow when checking assignability of recursive aliases

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6145 
 
 
 
  Stack overflow when checking assignability of recursive aliases  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6160) Triage 3.x acceptance failure

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6160 
 
 
 
  Triage 3.x acceptance failure  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6160) Triage 3.x acceptance failure

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6160 
 
 
 
  Triage 3.x acceptance failure  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Created:
 

 2016/04/12 8:28 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
3.x acceptance was broken for other reasons for a few weeks, and now that it has sprung back it's failing in future parser acceptance only, on rhel6: 
https://jenkins.puppetlabs.com/view/client%20triage/job/legacy_puppet_integration-system_future-parser_3.x/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 
 
The PVariantType#generalize method is generalizing all types. In this case, that results in three generalized integers. A new PVariantType is created with these three types and the constructor calls uniq on the array of types. One type remains. 
In general, I think calls to PVariantType#new should be avoided in favor of a method that first does uniq and checks if only one element remains. That will solve this problem and probably some others too. It's still in scope for this JIRA. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4039) package resource doesn't find new packages in yum repo

2016-04-12 Thread Robin Bowes (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robin Bowes commented on  PUP-4039 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 
 
I would also add that $current_client is on EL6 
R. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 
 
That is odd. Investigating... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6133) Unexpected result when accessing a hash using a Struct type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6133 
 
 
 
  Unexpected result when accessing a hash using a Struct type.   
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6133) Unexpected result when accessing a hash using a Struct type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6133 
 
 
 
  Unexpected result when accessing a hash using a Struct type.   
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6133) Unexpected result when accessing a hash using a Struct type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to John Duarte 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6133 
 
 
 
  Unexpected result when accessing a hash using a Struct type.   
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 qa John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 
 
I missed your last sentence. If this is already done in inference - then why does Iterator not benefit from that? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 
 
You would not write types manually that way, and if you did, it is actually better if it is shown. The issue is in inference which leads to output of types like Iterator[Variant[Integer]]. I think this should be solved on the inference side, not the presentation side. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6159) OSX Passwords not setting under Puppet 4 and OSX

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6159 
 
 
 
  OSX Passwords not setting under Puppet 4 and OSX   
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 
 
All normalizing will be wasted resources in a system where there's nothing to normalize. Unless you're sloppy when designing types, the types that will actually change during the normalization will be very few. Hence my concern. Who writes a variant with only one type in it, and why? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6148) Callable#assignable? results in undefined method `assignable?' for nil:NilClass

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6148 
 
 
 
  Callable#assignable? results in undefined method `assignable?' for nil:NilClass  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6147) PStructType#assignable? ignores Hash key type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6147 
 
 
 
  PStructType#assignable? ignores Hash key type.  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6146) PStructType#assignable? may return nil when compared against a Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6146 
 
 
 
  PStructType#assignable? may return nil when compared against a Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6145) Stack overflow when checking assignability of recursive aliases

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6145 
 
 
 
  Stack overflow when checking assignability of recursive aliases  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6133) Unexpected result when accessing a hash using a Struct type.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6133 
 
 
 
  Unexpected result when accessing a hash using a Struct type.   
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4039) package resource doesn't find new packages in yum repo

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4039 
 
 
 
  package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4039) package resource doesn't find new packages in yum repo

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4039 
 
 
 
  package resource doesn't find new packages in yum repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1375) Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes

2016-04-12 Thread Sean Griffin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Sean Griffin 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1375 
 
 
 
  Facter 3 improperly recognizes 0.0.0.0/X (X != 0) as default routes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 qa Sean Griffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6151) Output of iterator type emits 'value' text after type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6151 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Output of iterator type emits 'value' text after type  
 
 
 
 
 
 
 
 
 
 
There is a choice between verbatim string (%s), which you sometimes want, and 'programmatic' (%p) which is really required in order to not output screwy things. The problem here is that the output of notice is API. IMO, it is currently wrong in picking (%s) for embedded strings (etc.) in containers. It should really do what String($something) does by default (which is (%p) for contained. 
The work around is to use notice String($something if you want appropriately quoted contained data. 
So, there are two formats to define for "instance of non textually-representable types" - %s, and %p.  
(And I think the scope of this ticket should be widened). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title

Henrik Lindberg commented on PUP-6157

Re: Reduce inferred Variant[T] to T in inference of Array and Hash

Assuming an inferred type is used at least once for a type match, the cost of normalizing would probably pay of (or at least be substantially offset by the fact that it makes the subsequent type checking simpler). Worst case though are normalizations that find nothing to reduce.
Seems like inference of collection that ends up with Variant[T] easily could normalize that to T without having to do a full normalization (which I assume takes Undef, NotUndef, etc. into account as well). For other outputs of type, the type function offers variations on the inference (degrees of reduction), and that could perhaps be used (or a conversion rule on Type). That would help with the more complex reductions.

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-6151) Output of iterator type emits 'value' text after type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6151 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Output of iterator type emits 'value' text after type  
 
 
 
 
 
 
 
 
 
 
Agree about the general part. Perhaps we should scope this differently and instead discuss what the %s format of all things Puppet really is? Do we have any guidelines? Any consistency? I think we should and I think it's important. Once we have that, then it will be easy to determine what's being discussed above. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6159) OSX Passwords not setting under Puppet 4 and OSX

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6159 
 
 
 
  OSX Passwords not setting under Puppet 4 and OSX   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 Managing the passwords for local users under OSX 10.9, 10.10 and 10.11 under puppet 4.4.1 fails when setting the salt, iterations and password. Steps to re-create:Used the following command to generate a user definition and saved it to test.pp{code :java }puppet resource user test >> test.pp{code}{code: java puppet }user { 'test':  ensure => 'present',  comment=> 'test',  gid=> '20',  groups => ['com.apple.sharepoint.group.2'],  home   => '/Users/test',  iterations => '46948',  password   => '9690da8dd8f90f6e3fed4f267c86110e29d75e8448efdacdee9bd5cc20f81a563c9e6c6c328694fac80910ba99508cc373525ac592b87fbec0ac1a1e26a51f01873c25f2450aa78e09c8498df0f11fa930c3f655e7aeed6bc61e8475ca84297b3a2273d31974ddd232e872d9b66be82d0246d094d60155c93c6b7a27ba1aa390',  salt   => '62133b77a7aeecf506ffe99d064b3f8c068344de0a619a573a871f2fd6fe9eaf',  shell  => '/bin/bash',  uid=> '503',}{code}When running puppet apply on the following definition I get the following errors: {code} Error: "\x96" on UTF-8Error: /Stage[main]/Main/User[test]/password: change from [old password hash redacted] to [new password hash redacted] failed: "\x96" on UTF-8Error: "\xA7" on UTF-8Error: /Stage[main]/Main/User[test]/salt: change from 6f13b4510093e89a0098eff8ee5d4bae3e1314ebf31064c101cd886ad8c2fab6 to 62133b77a7aeecf506ffe99d064b3f8c068344de0a619a573a871f2fd6fe9eaf failed: "\xA7" on UTF-8Error: "\xD2" followed by "\x01" on UTF-8Error: /Stage[main]/Main/User[test]/iterations: change from 43290 to 46948 failed: "\xD2" followed by "\x01" on UTF-8 {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6156) Access operator is not implemented for Iterator type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 
 
And on to master. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6156) Access operator is not implemented for Iterator type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6156 
 
 
 
  Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

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 (PUP-6102) A type alias that has an alias name of a built-in type should be illegal

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6102 
 
 
 
  A type alias that has an alias name of a built-in type should be illegal  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 It is now illegal to attempt to redefine an already defined type. For example, type String = Integer, will now fail instead of causing mysterious problems. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title

Thomas Hallgren commented on PUP-6157

Re: Reduce inferred Variant[T] to T in inference of Array and Hash

It means that in most cases, the output will already be normalized. It's only when directly using the #to_s form of a type that strings like the above example will be visible. Then of course, this is not just about visibility. It might be beneficial to normalize for other reasons. Doing it excessively is resource consuming though so the difficulty in resolving this issue is to decide how to balance that:

Do we expect the system to contain lots of types that are in need of normalization?

If we don't expect that, is it enough that they are normalized when a type mismatch is printed (this already happens)?

Do we want to always normalize the type when producing it as a string?

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6156) Access operator is not implemented for Iterator type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 
 
Merged to stable at: 4a29182 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6151) Output of iterator type emits 'value' text after type

Title: Message Title

Henrik Lindberg commented on PUP-6151

Re: Output of iterator type emits 'value' text after type

quotes are unfortunately missing in a couple of places where they are needed (strings in arrays/hashes are kind of screwing things up if you are unlucky) - e.g. notice ['the end is near ]', 'wtf']. Also, since notice, when given multiple arguments do not add delimiters, the result can become quite strange depending on what precedes and follows output. We cannot mess too much with the format as that would blow up hundreds of tests, but we can ensure, in cases like this, that each output unit is seen as one unit of output.
The absolutely simplest change we can make to meet the requirement "one unit" is to add a hyphen in the current output - i.e.

Iterator[Variant[Integer]]-value

While this may seem as trivia, it tripped up Peter, then me until we understood the meaning of the "extraneous" 'value' output.
This discussion is also interesting in general - should we always output Object types in full, or state that they are 'instance of' ? And we we do output, we need to make it one unit of output by using delimiters - if not quotes then maybe enclose in parentheses. When we have decided on the style there, we should do the same here. (While not terribly important for the corner case of Iterator, it should be a principle we follow for the sake of consistency for anything that has a non-existing, non-obvious or complex textual representation). Had it just been Iterator then, meh, shrugs...

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6156) Access operator is not implemented for Iterator type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6156 
 
 
 
  Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 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 (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 
 
Which means? That it is really easy to fix this, or something else? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6156) Access operator is not implemented for Iterator type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6156 
 
 
 
  Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 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 (PUP-5928) Add pattern matching to Runtime Type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5928 
 
 
 
  Add pattern matching to Runtime Type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

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 (PUP-5928) Add pattern matching to Runtime Type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5928 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add pattern matching to Runtime Type  
 
 
 
 
 
 
 
 
 
 
Merged to master: 03a721d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5928) Add pattern matching to Runtime Type

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5928 
 
 
 
  Add pattern matching to Runtime Type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 This is a highly specialized feature that can be considered  an  internal  feature . You have to be super expert to benefit from this. It is also part of the larger Pcore feature. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6149) Parameterized Collection type is incorrectly constructed