Issue #14338 has been updated by Ken Barber.

Status changed from Accepted to In Topic Branch Pending Review
Assignee set to Ken Barber
Branch set to https://github.com/puppetlabs/facter/pull/197
Affected Facter version set to 1.6.8

Merge request here:

<https://github.com/puppetlabs/facter/pull/197>
----------------------------------------
Bug #14338: Some failures can't be traced any more
https://projects.puppetlabs.com/issues/14338#change-62048

Author: Ken Barber
Status: In Topic Branch Pending Review
Priority: Normal
Assignee: Ken Barber
Category: binary
Target version: 1.6.x
Keywords: 
Branch: https://github.com/puppetlabs/facter/pull/197
Affected Facter version: 1.6.8


I believe since we've changed the way we collect errors, we can't get stack 
traces when there are problems. For example:

    Facter.add("foobar") do
      setcode do
        nil.foobar
      end
    end

Will return:

    # facter  --trace
    Could not retrieve foobar: undefined method `foobar' for nil:NilClass
    architecture => x86_64
    domain => local
    facterversion => 1.6.8

In the past --trace would do the right thing and give us a trace.


-- 
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.

Reply via email to