Patrik Ragnarsson

Late to the party but I just wanted to say I very much liked your write-up here @schneems – thanks for taking the time for that ❤️ > To this...

CI has been flaky until recently, but I think it is in pretty good shape now actually, but ruby-head just started failing (https://github.com/puma/puma/pull/3418#issuecomment-2198241565), so we have to overlook that (I...

Thank you @ShadowJonathan for the very thorough analysis above. Reading that, this feature doesn't sound like a good fit for Puma.

What's the reason for removing old Rubies? I mean, once built, they wont stop working until the OS version disappears? Is it because users expect the very old Rubies to...

Puma still has [`required_ruby_version >= 2.4`](https://github.com/puma/puma/blob/1519350f9dafa511743d34bf673046bce08aadea/puma.gemspec#L36C51-L36C57). (It has been [suggested](https://github.com/puma/puma/discussions/3390) to raise it considerably)

It is a bit strange that the configuration is printed twice ([it wasn't with Puma 6](https://github.com/puma/puma/issues/3730#issuecomment-3330656294)) and that `preload_app` first is `false` but then `true` the second time. ```shell $...

Nice How I tested this branch I did `kill $(cat /tmp/puma)` while the request was running ```shell $ echo 'force_shutdown_after 5; shutdown_debug(on_force: true); app { |env| sleep 120; [200, {},...

I see what you mean :) Sure

We have this (almost)? https://github.com/puma/puma/blob/7aadde56fb2507dc0aab36649bc808a90c626e05/lib/puma/launcher.rb#L487 If `PUMA_LOG_CONFIG` is set the final config options are printed at start

Should it be a `pumactl` command so you are asking a running Puma about its config? Otherwise it doesn't make that much sense to me