Puppet Community

I pledge my gift card to voxpupuli :slightly_smiling_face:

faces is kinda cool. I've used it to add a new internal subcommand

it's not the first time I've seen the idea, but it's one of the nicer interfaces for it

<@U020LK7D0JU>++ well that means that VoxPupuli++ is our first winner!

That’s what I’d like to see in PDK btw

TBH I’m not a fan of the faces implementation. As a concept, its fine, easily create puppet applications and handle command line options. But imo the faces code it’s pretty terribad.

based on the number of times I inadvertently broke it with eg help string formatting or the like.... it doesn't surprise me that it was fragile.

I know, but I had to opt out of the hackathon this go-round so I'll stay quiet.

hahaha. I remember that one. it's not still in the code base, is it?

sadly no. But I resurrected it as a silly module, lol

if you have some ideas, you can kick out a starter PR today and mark it draft

the seeds of great ideas can be just as useful/productive

I clearly chose the easiest of the rubocop_todo's to fix

```pdk (INFO): Using Ruby 2.7.7
pdk (INFO): Using Puppet 7.23.0
[✔] Preparing to run the unit tests.
/opt/puppetlabs/pdk/private/ruby/2.7.7/bin/ruby -I/home/jstraw/.pdk/cache/ruby/2.7.0/gems/rspec-core-3.12.2/lib:/opt/puppetlabs/pdk/share/cache/ruby/2.7.0/gems/rspec-support-3.12.0/lib /home/jstraw/.pdk/cache/ruby/2.7.0/gems/rspec-core-3.12.2/exe/rspec --pattern spec/\{aliases,classes,defines,functions,hosts,integration,plans,tasks,type_aliases,types,unit\}/\*\*/\*_spec.rb --format progress

An error occurred while loading ./spec/unit/puppet/provider/ini_setting/inheritance_spec.rb.
Failure/Error: class Puppet::Util::IniFile::Section

Puppet::Error:
  Could not autoload puppet/type/inherit_ini_setting: Could not autoload puppet/provider/inherit_ini_setting/ini_setting: Could not autoload puppet/type/ini_setting: Could not autoload puppet/provider/ini_setting/ruby: uninitialized constant Puppet::Util::IniFile
# ./lib/puppet/util/ini_file/section.rb:6:in `&lt;top (required)&gt;'
# ./lib/puppet/util/ini_file.rb:4:in `&lt;top (required)&gt;'
# ./lib/puppet/provider/ini_setting/ruby.rb:3:in `&lt;top (required)&gt;'
# ./lib/puppet/type/ini_setting.rb:6:in `&lt;top (required)&gt;'
# ./spec/fixtures/inherit_ini_setting/lib/puppet/provider/inherit_ini_setting/ini_setting.rb:3:in `&lt;top (required)&gt;'
# ./spec/fixtures/inherit_ini_setting/lib/puppet/type/inherit_ini_setting.rb:1:in `&lt;top (required)&gt;'
# ./spec/unit/puppet/provider/ini_setting/inheritance_spec.rb:9:in `&lt;top (required)&gt;'
# ------------------
# --- Caused by: ---
# NameError:
#   uninitialized constant Puppet::Util::IniFile
#   ./lib/puppet/util/ini_file/section.rb:6:in `&lt;top (required)&gt;'

An error occurred while loading ./spec/unit/puppet/provider/ini_setting/ruby_spec.rb.
Failure/Error: class Puppet::Util::IniFile::Section

Puppet::Error:
  Could not autoload puppet/provider/ini_setting/ruby: uninitialized constant Puppet::Util::IniFile
# ./lib/puppet/util/ini_file/section.rb:6:in `&lt;top (required)&gt;'
# ./lib/puppet/util/ini_file.rb:4:in `&lt;top (required)&gt;'
# ./lib/puppet/provider/ini_setting/ruby.rb:3:in `&lt;top (required)&gt;'
# ./spec/unit/puppet/provider/ini_setting/ruby_spec.rb:6:in `&lt;top (required)&gt;'
# ------------------
# --- Caused by: ---
# NameError:
#   uninitialized constant Puppet::Util::IniFile
#   ./lib/puppet/util/ini_file/section.rb:6:in `&lt;top (required)&gt;'

An error occurred while loading ./spec/unit/puppet/provider/ini_subsetting/ruby_spec.rb.
Failure/Error: class Puppet::Util::IniFile::Section

Puppet::Error:
  Could not autoload puppet/type/ini_subsetting: Could not autoload puppet/provider/ini_subsetting/ruby: uninitialized constant Puppet::Util::IniFile
# ./lib/puppet/util/ini_file/section.rb:6:in `&lt;top (required)&gt;'
# ./lib/puppet/util/ini_file.rb:4:in `&lt;top (required)&gt;'
# ./lib/puppet/provider/ini_subsetting/ruby.rb:3:in `&lt;top (required)&gt;'
# ./lib/puppet/type/ini_subsetting.rb:5:in `&lt;top (required)&gt;'
# ./spec/unit/puppet/provider/ini_subsetting/ruby_spec.rb:6:in `&lt;top (required)&gt;'
# ------------------
# --- Caused by: ---
# NameError:
#   uninitialized constant Puppet::Util::IniFile
#   ./lib/puppet/util/ini_file/section.rb:6:in `&lt;top (required)&gt;'

An error occurred while loading ./spec/unit/puppet/util/ini_file_spec.rb.
Failure/Error: class Puppet::Util::IniFile::Section

NameError:
  uninitialized constant Puppet::Util::IniFile
# ./lib/puppet/util/ini_file/section.rb:6:in `&lt;top (required)&gt;'
# ./lib/puppet/util/ini_file.rb:4:in `&lt;top (required)&gt;'
# ./spec/unit/puppet/util/ini_file_spec.rb:5:in `&lt;top (required)&gt;'```

<@U11HA7VJ7> I have a feeling some of this rubocop_todo stuff is actually unfixable and is actually how puppet expects to do things, stuff like RSpec/NamedSubject ; RSpec/ImplicitSubject; and some of the Metrics stuff

basically, this is saying that you cannot create `Puppet::Util::IniFile` until `Puppet::Util` exists

yea, so if you do module Puppet::Util it works, but rubocop yells

if you added
```class Puppet::Util
end```
before it, then it should work, but that's stupid.

in my opinion, add an inline comment to ignore this one

Maybe raise a ticket for someone to investigate because basically what this means is that this is being loaded before Puppet's fully initialized and that seems potentially problematic too.

how about Metrics/* which all really hate Puppet's dispatch system because it adds boilerplate

where would you like the ticket :slightly_smiling_face:

I'm assuming this is the inifile module; put it in that github repo

I wasn't sure if you wanted it there or somewhere more global because I am sure inifile isn't the only place this has issues

<https://github.com/search?q=org%3Apuppetlabs+path%3A.rubocop_todo.yml+ClassAndModuleChildren&amp;type=code> 11 files

This is the same violation, but it's not fragile in the way I noticed above. <https://github.com/puppetlabs/puppetlabs-lvm/blob/main/lib/puppet_x/lvm/output.rb#L1-L4>

it's also a question of which format to use, clearly puppet uses concise, but I think the default is nested

this is _creating_ the `Puppet_X::LVM` class and then the `::Output` subclass.

the other one is intended to be adding a subclass to `Puppet::Utils` , but by accident is actually _creating_ it and what should be the original class definition ends up monkeypatching it

and I think that's by design to some degree, because Puppet::Utils exists in the ether at that point

Puppet_X::LVM would be a specific sub module of Puppet_X created in that module

I often wish that it wasn't quite so easy to monkeypatch in Ruby, lol

Puppet::Util seems like a worst case scenario of overlapping overloaded modules

<https://github.com/puppetlabs/puppetlabs-inifile/issues/509>

<https://github.com/puppetlabs/puppetlabs-inifile/pull/510> for a bunch of heredoc fixes and the end of my hackathon time

Japanese hard rock from the 70s :grin: Like Flower travellin band. Also hard rock from the same time from other parts of the world.

Early 90s hip-hop over here :headphones:.

heh. I'm listening to air tools in the background. Have a contractor out building a new fence.

the best music, work you're not having to do

Non-vocal trance or ambient or mantras.. just remind me I should subscribe to <http://di.fm|di.fm> premium (epic trance channel iirc).. though DJ Basilisk’s Colours of Ektoplazm mix is good for 5hrs of work too :)

I'm going for a Japanese Trance mix today &lt;<https://www.youtube.com/watch?v=YjBDv7Lj4kc>&gt;

A quich fix for code merged  a few hours ago: <https://github.com/puppetlabs/puppetlabs-stdlib/pull/1351>

Luke started the consulting company that would evolve into Puppet due to frustrations working in IT for CAT in Nashville. This was ~ 2005

<https://www.oregonlive.com/siliconforest/2010/03/reductive_labs_takes_new_name.html>
&gt; Reductive Labs takes new name: Puppet Labs
Reminded me the older name… Then internet archive helped: looked for a contact page older than this move date. :stuck_out_tongue:

in 2009, he moved the company to Portland, and in 2010 pivoted to building the tool that he'd been developing for his customers and taking on the name Puppet Labs in the process.

<@U11HA7VJ7> <@U0332SZQLKZ> :: Here is my Draft PR just to get things started. Didn’t make much progress in testing but will definitely try and cycle back to this one soon! :slightly_smiling_face: <https://github.com/puppetlabs/pdk/pull/1246>

one more hour and then we'll close up shop here. Anyone still hacking away?

All right, let's go ahead and close this up! I'll have a couple closing words if people are still online.

image (16).png

Just realized that we forgot to announce that <@UBLSQB5FB> wins :darthvader: for the most impactful PR even though the work wasn't all done yesterday. It was a real tossup between that and <@U6B5Q9BSA>'s "let's just modernize all of stdlib" mission!

bert0214 leveled up! (Karma: 1)
smortex leveled up! (Karma: 7)

Hey all,

On behalf of the Puppet team, thank you again for participating! :clapping:  It was a pleasure to hang out with you in this hackathon!

Next week we will be sending the stickers, a post-event survey (for future improvements) and for the prize winners, you can expect some follow-up next week :awesome:

Have a lovely Friday! :puppetparrot:

Hi Puppet Community :wave_:

It’s been a week since our last hackathon. We value your feedback and would greatly appreciate your input to enhance our upcoming Puppet event.

Please take a moment to complete this brief survey, which should only take a maximum of 2 minutes of your time.

:point_right: <https://forms.gle/pWKYY9W81J5gZxJ69>   Thanks!!

Nice one… I’ve kicked off the ci :clock1: 

left a comment.. Looks like some weirdness went on with the merge conflict too :+1:

great, yea I don't know what the heck my merge conflict failed on

ok, so I fixed it and got an error I can't quite diagnose (that doesn't look related)

May the Source Be With You, 2024!
It's Star Wars Day again, and we usually do a hackathon to celebrate. This year it falls on a weekend...