Issue #6928 has been updated by Daniel Pittman.
Oh. That clarifies things. I only tested 1.8.7, our default version, because there was no hint of another version being used in the original report. At least, none that I noticed. I would vote for backporting Symbol#to_proc, if it was easy, since it fits the general policy of backporting language features rather than getting stuck with the lowest common version, but whatever. Fixing validate is easy enough too. If no one else gets to it first I will attend to this tomorrow. ---------------------------------------- Bug #6928: Puppet master --parseonly does not detect manifest errors https://projects.puppetlabs.com/issues/6928 Author: Dominic Maraglia Status: Re-opened Priority: High Assignee: Nigel Kersten Category: Target version: Statler Affected Puppet version: development Keywords: puppet master parseonly Branch: puppet=>"2.6.7-40-gd7a1424" facter=>"1.5.8" Give an invalid manifest such as: <pre> class foo { file { "foobar": ensure => file. content => "blah" </pre> puppet --parseonly detects the bad manifest: <pre> [root@cent-55-64-1 puppet]# puppet --parseonly ./foo.pp ; echo $? err: Could not parse for environment production: Syntax error at '.'; expected '}' at /etc/puppet/foo.pp:5 1 </pre> puppet master --parseonly does not detect the error: <pre> [root@cent-55-64-1 puppet]# puppet master --parseonly ./foo.pp ; echo $? 0 </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
