Lissa Moriarty

It is indeed that bug. Please upvote it, as nobody seems to be paying it any attention at the moment. The problem is that $LOAD_PATH isn't set up before types/providers...

On Puppet 3.8 I'm currently working around this with a hack module, adding a parser function which affects the Puppetmaster's Ruby environment: ```ruby require 'puppet/util/autoload' module Puppet::Parser::Functions newfunction(:libfix) do |args|...

I've hit this when using `let!` in `shared_context`, which is the reverse situation.

We use `let!`, for example, to set something up that needs to be present before `before` is executed, and that we also need to reference in the tests. Here's a...

I'm using 1.42.0 and it's giving me it for that example (when I remove the rubocop:disable marker): ``` Inspecting 1 file C Offenses: spec/test.rb:1:1: C: Style/FrozenStringLiteralComment: Missing frozen string literal...

Yes, to clarify, the original issue was with regards to setting up multiple front-ends which share the same database and filestore (for clustering). Building an additional node wipes the database...