Jira (PUP-3032) Setting to cache `load_library` failures

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on an issue   Re: Setting to cache `load_library` failures I think there are a few things to verify here. Create a module that installs a gem using a package resource: package { 'mygem': ensure => installed, provider => gem } defines a feature based on the gem: Puppet.features.add(:myfeature, :libs => "mygem") and defines a type and provider that is confined based on the feature: Puppet::Type.newtype(:something) do newparam(:name, :namevar => true) newproperty(:myprop) end Puppet::Type.type(:something).provide(:whatever) do confine => myfeature def myprop end def myprop=(value) end end And defines a resource based on the type & provider: something { 'myname': provider => whatever } This is similar to our ticket_6907_use_provider_in_same_run_it_becomes_suitable acceptance test, however, that uses an external command, not a feature. But it's a good point of reference for verifying this fix. If always_cache_features is false, we should be able to install the gem, and use the provider within a single run. If always_cache_features is true, the provider should not be suitable as determined at the start of the puppet run, and puppet should generate an error. Change the feature definition to use a block, e.g. Puppet.features.add(:myfeature) do require "mygem" end For historical reasons, puppet has always cached the result when using a block... So puppet should generate an error that there is no suitable provider regardless of what always_cache_features is set to. Ideally this should be part of a spec test, but I don't believe all of these cases are currently covered. Add Comment   Puppet / PUP-3032 Setting to cache `load_library` failures See related PE ticket; this is just a placeholder to make sure we try to get something in for this in time for 3.7.0. In `rubygems.rb`, there are some calls to `Gem.clear_paths`. This is potentially a very expensive operation as it can cause ruby to have to examine all of the files in the entire gem load_path in order to rebuild its internal directory ... 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/d/optout.