[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-12-03 Thread tickets
Issue #22729 has been updated by Melissa Stone. Released in Puppet 3.4.0-rc1 Bug #22729: New future-parser-only functions are loaded although one is not using the future parser https://projects.puppetlabs.com/issues/22729#change-100531 * Author: Peter

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-12-03 Thread tickets
Issue #22729 has been updated by Melissa Stone. Released in Puppet 3.4.0-rc1 Bug #22729: New future-parser-only functions are loaded although one is not using the future parser https://projects.puppetlabs.com/issues/22729#change-100616 * Author: Peter

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-12-03 Thread tickets
Issue #22729 has been updated by Melissa Stone. Released in Puppet 3.4.0-rc1 Bug #22729: New future-parser-only functions are loaded although one is not using the future parser https://projects.puppetlabs.com/issues/22729#change-100754 * Author: Peter

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-12-03 Thread tickets
Issue #22729 has been updated by Melissa Stone. Released in Puppet 3.4.0-rc1 Bug #22729: New future-parser-only functions are loaded although one is not using the future parser https://projects.puppetlabs.com/issues/22729#change-100798 * Author: Peter

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-12-03 Thread tickets
Issue #22729 has been updated by Melissa Stone. Released in Puppet 3.4.0-rc1 Bug #22729: New future-parser-only functions are loaded although one is not using the future parser https://projects.puppetlabs.com/issues/22729#change-100929 * Author: Peter

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-10-09 Thread tickets
Issue #22729 has been updated by Henrik Lindberg. Target version set to 3.4.0 Branch changed from https://github.com/puppetlabs/puppet/pull/1970 to https://github.com/puppetlabs/puppet/pull/1985 A decision was made to instead remove the iterative future parser function called 'reject' as it

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-10-04 Thread tickets
Issue #22729 has been updated by Henrik Lindberg. Branch set to https://github.com/puppetlabs/puppet/pull/1970 While not fixing the larger issue; that functions requiring the future parser can be called when not using it, the pull request https://github.com/puppetlabs/puppet/pull/1970 at

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-10-02 Thread tickets
Issue #22729 has been updated by Henrik Lindberg. It is difficult to provide an easy fix for this because there is no mechanism in the auto loader to make it continue its search if a found file contains something that is disqualified. An implementation could raise an exception (or throw

[Puppet - Bug #22729] New future-parser-only functions are loaded although one is not using the future parser

2013-09-29 Thread tickets
Issue #22729 has been updated by Henrik Lindberg. Ouch, that is bad, will look into how to best skip definition of a function in these cases. The issue with a name clash vs. the reject function in stdlib requires some additional thought. Bug #22729: