s

I had a thing where trying to run acceptance tests on CentOS locally in Docker (with CentOS 8) was making Docker crash, and now is erroring with "EOFError (EOFError)" after the first phase runs and /sbin/init runs... not seeing anything obvious about it from a web search. ring a bell for anyone?

Also, I logged into an old screen session, and... wowzers. I was the only person left in the channel, and there were all kinds of offensive messages going on. Did something get messed up with one of the libera nodes?

morning

wby: sounds odd. You can always report that to #libera

Are there any other forge-server implementations besides unibet/kindregroup forge-server? Both dont receive updates for quite some time. Are there any other alternatives besides JFrog or Nexus?

Just created https://github.com/voxpupuli/puppet-mongodb/pull/677 Is it appropriate to post this here ? Still work in process, currently making it past all tests. Any advise/comments are welcome. Still in 'it works for me now' state

This message was deleted.

all the best

and what are your plans for the future?

bastelfreak: https://github.com/voxpupuli/rspec-puppet-facts/pull/151 I think it's now ready and I feel confident in the tests, but would appreciate it if someone did some testing on real modules

I think the solution ended up being fairly elegant with first a strict filter and then a loose fallback so it's doable to follow

I will try to check that

and please look at the loose requirement conversion: I chose to ignore patch versions in loose requirements, allowing it to use 3.9.6 if 3.9.5 was requested but not found, but perhaps there should be an intermediate selection too where it prefers 3.9.[0-4]

since facter 3 I don't think this is much of a concern for us

so 3.9.5 could be: try ~> 3.9.5.0, fall back to >= 3.9.0 <= 3.9.5 (with warning that it's falling back), fall back to <= 3.9.5 (with warning that it's falling back)

I had the same thought

@ewoud: do you have some experience with https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/fileparsing.rb?

can't say that I do

How do people mock Puppet 4x API Ruby functions in rspec? All of the existing examples I could find were for the old Ruby function API, e.g.

Puppet::Parser::Functions.newfunction

. I'm specifically trying to override the function code of an existing 4x API Ruby function. This seems to work, but I'm wondering if there's an easier/better way:

RSpec.configure do |c|
  c.before :each do
    allow(Puppet::Pops::Loader::RubyFunctionInstantiator).to receive(:create).and_wrap_original do |original, loader, typed_name, source_ref, ruby_code_string, &_block|
      if typed_name.name == 'mocked_function'
        ruby_code_string = 'Puppet::Functions.create_function(:mocked_function) do
          def mocked_function(*_args)
            'mocked value'
          end
        end'
      end
      original.call(loader, typed_name, source_ref, ruby_code_string)
    end
  end
end

can I get a review for https://github.com/voxpupuli/voxpupuli.github.io/pull/303/files

https://voxpupuli.org/sponsoring/ nice, impressive list

bastelfreak: thanks for the review :). I wanna get https://github.com/voxpupuli/puppet-falco/pull/25 and https://github.com/voxpupuli/puppet-falco/pull/26 out for solving the same issues I'm running into, and might as well include https://github.com/voxpupuli/puppet-falco/pull/23 from the same user. Looks like you're good with #26 & #23, so anything more about #25 to update?

Hunner: when its wrapped in a condition, is ensure_packages required or could we drop that?

because thats deprecated in stdlib 9

Oh it's deprecated? What pattern replaces ensure_packages()?

It's got the condition around it now

But I totally agree with you that clang/llvm/dkms are kind of generic. But they're also required for this thing to work

it is now namespaced as stdlib::ensure_packages

Ooo just a namespaced function. If that was introduced long enough ago I can just substitute that