Issue #14443 has been updated by Andrew Parker. Status changed from Unreviewed to Accepted
---------------------------------------- Feature #14443: Always produce a backtrace on unhandled errors https://projects.puppetlabs.com/issues/14443#change-63927 Author: Andrew Parker Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: Right now puppet will write errors to the log file such as err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Variable failed with error NoMethodError: undefined method `twoscope_lookupvar' for nil:NilClass at /etc/puppet/site/modules/[...]/init.pp:2863 on node [...] In any case like this we need to make sure that there is always a backtrace available with the unhandled error. Quite often it is difficult to get a reproduction of the error from a user that might produce the backtrace and so debugging the issue can become nearly impossible. We should also consider producing some other information what would be useful for a bug report in this case. -- 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.
