Patrik Ragnarsson
Patrik Ragnarsson
I guess the issue is https://github.com/fxn/zeitwerk/commit/8f37a65ee5c18f0fa3e1bf28283e8ee4b1b9b39e
@DawidJanczak Yes it is broken, @fxn changed the path in 2.7.0, the one you added earlier, we need to account for the new location too. I haven't gotten to it....
Is there anything needed to be done in Puma to support this?
You start Puma by running `puma`? Or ``bundle exec puma`` Have you seen https://github.com/puma/puma/blob/master/docs/systemd.md?
I'm not using systemd myself so I'm not sure. Maybe you can test it and report back. Maybe you can even improve the docs if there's need for that. This...
I don't think anything needs to happen in Puma to accomplish this, so I'll close the issue. Happy to be proven wrong though!
Is `update_worker_count` a good name? Could it be confused with worker _processes_? How would one use this? Could you show an example dummy app using this?
I can also confirm the long tail is gone! How I started Puma: `echo 'app { sleep(0.2); [200, {}, ["OK"]] }' | ruby -Ilib bin/puma -w 0 -t 5:5 --config...
> The turbo-rails failures are due to changes in Ruby head with the `Set` class. Do you have a link? Or is it broken and will be fixed?
I see, https://github.com/ruby/ruby/pull/13074 had a bug but https://github.com/ruby/ruby/pull/13185 will fix it.