Rosa Gutierrez

Hey @paulhtrott, ohhhh, thanks for letting me know! It's a bummer it didn't solve it completely, but I'll take the reduction. I'll merge that and will start using it in...

Ohhh, @paulhtrott, that's super helpful! This looks like a different kind of deadlock than the one I tried to fix! Let me try to put together another fix for this...

That deadlock is the same one as https://github.com/rails/solid_queue/pull/229, going to tweak that one a bit and ship.

@paulhtrott, I just released version 0.3.3 with a possible fix for this one deadlock: #240.

Ohh, bummer 😞 I'll continue working on it. Thanks a lot for letting me know!

Oh, @paulhtrott, I realised something... The query done now to delete records from `solid_queue_ready_executions` should be using the primary key instead of `job_id`, so I wonder if the locks that...

Hey @hms! There's not a good way right now to terminate a worker alone besides sending the `TERM` or `QUIT` signal as you're doing. Either of these will signal the...

> I'm calling terminate via an around perform, so in theory, the worker shouldn't be requesting new work and should be running through its cleanup protocol. ... > Question: Since...

Hey @hms, so sorry for the radio silence on this one! Your last comment totally slipped through the cracks as it got me travelling for two weeks, and then I...

Hey @carsoncole, sorry about that! Could you share a bit more about your DB setup? Also, could you try setting this: ```ruby config.solid_queue.silence_polling = false ``` And then starting `solid_queue:start`...