but that's a pdk style module

which means it has something like

gem "puppet-module-posix-default-r#{minor_version}"

in the Gemfile

the gems depend on the ruby version. no release for ruby 3.0/ruby 3.1

https://tickets.puppetlabs.com/browse/MODULES-11161 and nobody cares about it since months, which basically blocks everybody with not-ancient software to test stuff on puppetlabs modules

@Philippe Beaumont ^ that's the kind of stuff I meant when I said I really don't like pdk

This message was deleted.

@Alex Fisher if I hack the Gemfile to assume I'm on ruby 2.7 it still fails:

Bundler found conflicting requirements for the Ruby version:
  In Gemfile:
    Ruby

    puppet-module-posix-system-r2.7 (~> 1.0) was resolved to 1.0.0, which depends on
      puppet_litmus (~> 0.20.0) was resolved to 0.20.0, which depends on
        bolt (< 3.0.0, >= 2.0.1) was resolved to 2.44.0, which depends on
          Ruby (~> 2.5)

of course bolt doesn't support ruby 3...

If I remove https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/puppet/functions/to_yaml.rb#L3 then it's better again...

If I remove https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/puppet/functions/to_yaml.rb#L3 then it's better again...

https://p.bastelfreak.de/mn2vE/ I see a lot of changes in the REFERENCE.md on ruby 3.1

There are the new functions that didn't include a change to REFERENCE.md in their PR. Fine. But https://p.bastelfreak.de/mn2vE/#n51 ??

and docs vanishing here. https://p.bastelfreak.de/mn2vE/#n143

If you move the

require 'yaml'

(or

require 'json'

depending on which function you're looking at), it works as expected. Also seems fine on older rubies.

yes I can confirm that

So... who's our puppet-strings expert these days?

cough ewoud cough cough.

sadly that's probably the correct answer 😄

and with that I'm off for diner o/

Why sad? ewoud's great! 🙂

It's not that important right now, but at some point someone will nuke those docs by accident if we do nothing.

I don't really like creating a PR to move some `require`s around because of a bug I can barely explain let alone understand.

bastelfreak: do you happen to run Puppet on Ruby 3.1?

after I upgraded to Fedora 36 (which uses Ruby 3.1) I get /usr/share/gems/gems/concurrent-ruby-1.1.5/lib/concurrent/atomic/ruby_thread_local_var.rb86in `new': can't alloc thread (ThreadError)

I also wonder if it has something to do with systemd limit that may have changed

if you find errors, can you add them to https://tickets.puppetlabs.com/browse/PUP-11406

I'm not sure it is Ruby 3.1 or not, but I'll see about creating a proper bug report and linking it there

it doesn't look like Fedora 36 has a Ruby 3.0 module so I don't think I can easily switch back

Arch is currently on 3.0 but I think I saw successful CI runs in the past with ruby 3.1

what is a CI run here? I see it when it runs as a daemon