Jira (FACT-1133) Facter.value of built-in facts causes unnecessary Ruby object allocations

[Peter Huene (JIRA)]

Title: Message Title

Peter Huene created an issue   Facter / FACT-1133 Facter.value of built-in facts causes unnecessary Ruby object allocations Issue Type: Bug Affects Versions: FACT 3.0.2 Assignee: Peter Huene Created: 2015/07/16 4:14 PM Fix Versions: FACT 3.0.3 Priority: Normal Reporter: Peter Huene In irb: .0.0-p598 :001 > require 'facter.rb' => true 2.0.0-p598 :003 > Facter.value(:os).object_id => 70330669917560 2.0.0-p598 :004 > Facter.value(:os).object_id => 70330669905200 2.0.0-p598 :005 > Facter.value(:os).object_id => 70330669884900 The object id changes because we're allocating a new Ruby object for the fact value. This is caused by not setting _resolved to true for resolving a fact already in the collection (i.e. a built-in fact). Add Comment   This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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/d/optout.