Rosa Gutierrez

> What's the easiest way to do this? Would an empty `recurring.yml` already disable the scheduler? @majkelcc yes! If you have no recurring tasks defined at all (the default), then...

@Jell, yeah, I still think the `async` mode I had was a good idea because of this... but it wasn't my call in the end. I'll see if I can...

Going to close this one in favour of #330, to fix a recent memory issue, and then I'll try to get that async mode with a single process eventually.

Oh, yes... `on_thread_error` is intended for Solid Queue's internal errors and wouldn't fit for this. In theory, you should only get process pruned errors when a process dies unceremoniously (killed,...

> like details of all the jobs that were in flight But these jobs are precisely the ones that fail with a `ProcessPrunedErrors`. > The general semantic that queues provide...

> "re-enqueue by default" safe. Sidekiq definitely re-enqueues and I thing Good job does too, though Resque I think does not. Kubernetes jobs do it. I think Celery does too....

Oh wow! I didn't imagine someone running into this 😕 What's your use case to need a custom adapter extending `solid_queue` adapter?

Oh, interesting! I'll eventually get to adding sharding support to Solid Queue. I was supposed to work on that last month but there was a change on plans 😅 Does...

Hey @ThomasCrambert, this is almost wired up but not exactly what you want, via [these not yet documented options](https://github.com/rails/solid_queue/blob/ef7b4d0cf8c8cab61a59692cece8e390d3e2bedc/lib/solid_queue/configuration.rb#L89-L91). If you don't specify any workers, it also works, you don't...

Ah, I meant that you can leave the `workers` attribute out completely, so you wouldn't need to specify these values (it'd behave in the same way as `processes: 0` and...