Issue #12359 has been updated by Daniel Pittman. Description updated
Updated description; this isn't just a testing concern, but actually makes it harder to extract that information in the field if you are trying to debug a problem. Being able to capture the trace automatically is not a bad strategy for helping us help users. ---------------------------------------- Refactor #12359: improve logging of backtraces https://projects.puppetlabs.com/issues/12359 Author: Chris Price Status: Accepted Priority: Low Assignee: Chris Price Category: Target version: Telly Affected Puppet version: Keywords: Branch: Add a utility method to Puppet::Util::Logging (or similar) that can be used for logging exceptions. Currently, there are a ton of places in the code where we do this: puts(exception.backtrace) if Puppet[:trace] This has a few problems: 1. It's not very DRY 2. The "puts" approach means that we always try to write the traces to stdout. When running via puppet master in daemon mode, this often results in the messages just getting thrown away. Debugging the Puppet Master and Agent daemons would be made much easier in certain cases if the traces were logged via the normal puppet logging framework rather than via puts. -- 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.
