Jira (PUP-4612) Error in future parser on non-interpolated strings

2015-05-17 Thread Dylan Cochran (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dylan Cochran assigned an issue to Dylan Cochran 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
Bug was due to invalid code updating farther down the CI path. Disregard 
 
 
 
 
 
 
 
 
 
 Puppet /  PUP-4612 
 
 
 
  Error in future parser on non-interpolated strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dylan Cochran 
 
 
 

Resolution:
 
 CannotReproduce 
 
 
 

Assignee:
 
 DylanCochran 
 
 
 

Status:
 
 Open Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group 

Jira (PUP-4620) Make it possible to use different versions of a data provider in different environments

2015-05-17 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4620 
 
 
 
  Make it possible to use different versions of a data provider in different environments  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/05/17 4:47 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
Currently, the binder loads code via the (3.x) autoloader. This means that it can only load one version of whatever it is loading across all environments. (It may try to load it again, possibly overwriting what was loaded earlier). This is far from ideal. 
It is better to migrate the loading of data providers to the new loaders, and to modify the API of the data providers to allow them to be anonymously loaded (like how 4.x functions are loaded). 
This requires some design work: 
 

It is probably best if loaders are configured to handle plugins in general as opposed to having one specialized loader per kind of plugin.
 

We are encouraging the use of PuppetX::Author as a namespace for implementations, but have no structure / rules under this namespace. If we introduce rules we risk finding the wrong thing in modules that do not comply with the new rules.
 

We do not want to search among all possible plugins when looking for a plugin of a particular kind.
 
 
 
 
 
 
   

Jira (PUP-4620) Make it possible to use different versions of a data provider in different environments

2015-05-17 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4620 
 
 
 
  Make it possible to use different versions of a data provider in different environments  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4613) Unclear language in the spec around types being assignable from types

2015-05-17 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4613 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Unclear language in the spec around types being assignable from types  
 
 
 
 
 
 
 
 
 
 
I added this to types_values_varibles.md in the section The Kinds of Types and Values (at the start of the document). 

When describing types, the term assignability (in different forms) is used to describe the relationship between two types such that a Type T is assignable from a type T2 if all possible values having type T2 are also values of type T. This can also be expressed as a type T2 is assignable to a type T, or T accepts T2 (as a short form of A variable typed T accepts an assignment of a value of type T2). As an example; The type Numeric is assignable from the type Integer.
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4613) Unclear language in the spec around types being assignable from types

2015-05-17 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4613 
 
 
 
  Unclear language in the spec around types being assignable from types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 NicholasFagerlund 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4570) Is the code ready for release?

2015-05-17 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4570 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Is the code ready for release?  
 
 
 
 
 
 
 
 
 
 
That's right - Client team has no tickets planned for 3.8.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4570) Is the code ready for release?

2015-05-17 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4570 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Is the code ready for release?  
 
 
 
 
 
 
 
 
 
 
Language tickets not yet done: 
 

PUP-4483
 

PUP-4552 (a QA ticket)
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4619) fstab entries can be written in bad order

2015-05-17 Thread Felix Frank (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Felix Frank created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4619 
 
 
 
  fstab entries can be written in bad order  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PUP 2.7.25 
 
 
 

Assignee:
 
 Felix Frank 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2015/05/17 1:19 PM 
 
 
 

Environment:
 
 
*NIX 
 
 
 

Fix Versions:
 

 PUP 4.x 
 
 
 

Labels:
 

 community 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Felix Frank 
 
 
 
 
 
 
 
 
 
 
Given the following fstab content in /tmp/fstab