The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #14338

Some failures can't be traced any more

Added by Ken Barber almost 2 years ago. Updated about 1 year ago.

Status:In Topic Branch Pending ReviewStart date:05/06/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:binary
Target version:2.x
Keywords: Affected Facter version:1.6.8
Branch:https://github.com/puppetlabs/facter/pull/197

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the FACT project on JIRA using the button below:


Description

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.

History

#1 Updated by Ken Barber almost 2 years ago

Actually – I’m wrong and it never really worked. Still, it should work.

#2 Updated by Ken Barber almost 2 years ago

  • 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

#3 Updated by Jeff Weiss almost 2 years ago

  • Target version changed from 144 to 2.1.0

This seems better suited to 2.1.0 rather than 1.6.10.

#4 Updated by Ken Barber almost 2 years ago

  • Assignee changed from Ken Barber to Andrew Elwell

#5 Updated by Ken Barber almost 2 years ago

  • Assignee deleted (Andrew Elwell)

#6 Updated by eric sorenson about 1 year ago

  • Target version changed from 2.1.0 to 2.x

Also available in: Atom PDF