Jira (FACT-349) Facter doesn't surface exception backtraces

[Joshua Cooper (JIRA)]

Title: Message Title

Joshua Cooper commented on an issue   Re: Facter doesn't surface exception backtraces I had an older version of facter-2 installed that had this bug and wasn't getting backtraces. Updated to the latest version, added nil.what to a resolution, and see the backtrace: $ be facter --trace Could not retrieve fact='swapencrypted', resolution='<anonymous>': undefined method `what' for nil:NilClass /Users/josh/work/facter/lib/facter/memory.rb:89:in `block (2 levels) in <top (required)>' /Users/josh/work/facter/lib/facter/util/resolution.rb:149:in `call' /Users/josh/work/facter/lib/facter/util/resolution.rb:149:in `resolve_value' Running without --trace just shows the top-level message as expected. Add Comment   Facter / FACT-349 Facter doesn't surface exception backtraces When an error is raised/caught inside of Facter, the majority of rescue locations cannot display backtraces. This makes it challenging to debug the origin of crashes and failures inside of Facter. With the upcoming Facter 2.0 release we expect some breakage in custom facts and the like, and it would be very helpful for users to see these traces while hand... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.