Rosa Gutierrez

Hey @dglancy! Could you send a `TERM` or `INT` signal to the process as described [here](https://github.com/rails/solid_queue?tab=readme-ov-file#threads-processes-and-signals)? That, combined with `SolidQueue.shutdown_timeout`, will try a graceful termination first, so workers won't pick...

Oops, sorry for the delay here! I missed the last notification back in October 😳 About the connection pool errors, the configuration now has a validation step for the connection...

Going to close this one as there's nothing else to do on the solid queue side! 🙏

Hey @p-schlickmann, yes. All these tests that fork processes and rely on waiting on things to happen elsewhere are quite flaky indeed. I don't have any particular suggestions to start...

Looks like the flakiest test after the last improvements is this one: ``` bin/rails test test/integration/instrumentation_test.rb:306 ``` I tried to make it better in https://github.com/rails/solid_queue/commit/f433a99fd402dd25213db445dbcebef29617aa8c but that didn't work so...

Hey @Austio, we do have one, https://github.com/rails/mission_control-jobs 😊

Hey @ericwecasa, sorry about this! When you say they jobs are _finished_, what do you mean exactly?

Hey @ericwecasa, so sorry for the delay! I missed that last comment 😳 This is really strange! I can't imagine how this can happen, because for a job to fail...

Hey @ThomasCrambert, thanks for this! I don't quite understand the use-case here 🤔 Could you provide more details about why do you need this? How do you handle other configurations?

> Which configurations are you referring to there? The ones for workers/dispatchers/schedulers? Yes, but also any other Rails configuration, because I didn't understand very well what you meant, so I...