solid_queue
solid_queue copied to clipboard
Database-backed Active Job backend
We are migrating to Solid Queue and trying to find out how to support our use case: We currently use sidekiq and a custom currency control that makes sure there...
I've had SolidQueue setup and working for awhile on a low traffic app. But I sporadically get a job that takes a long time to complete (I just had one...
## Summary The concurrency controls that currently exist allow blocking execution of "duplicate" jobs, or jobs with the same arguments. These jobs wait, then execute after the currently running job...
Hi @rosa, I really appreciate the work you have done here and I am eager to switch over to solid_queue. There is only one thing left, which is holding me...
Hi there, Note that I have SolidQueue already installed in my project, so upgraded to 0.3.0 which installed fugit. After running the migrations to add the new table/indices, starting up...
Yes, I think `silence_queries` would work 👍🏻 _Originally posted by @rosa in https://github.com/rails/solid_queue/issues/198#issuecomment-2048122748_ As mentioned in #198, `silence_polling` only silences the polling queries (which makes sense), and continues to log...
I have added `config.solid_queue.silence_polling = true` in my `application.rb` I have restarted my server after that. But still I am getting logs as following ``` solid_queue_1 | SolidQueue::Pause Pluck (1.4ms)...
I ran into a problem with passing an ActiveSupport::Duration to a recurring job. I built a couple of jobs that just pass arguments and check that they are received as...
Is there any way of detecting (from outside of the process) when the worker process is up and running and able to start processing jobs? During deployment on Kubernetes a...