solid_queue
solid_queue copied to clipboard
basecamp
Database-backed Active Job backend
Solid Queue's internal queueing mechanism makes it a good fit for Active Job, and can serve as a replacement for Redis-backed job queues. Are there also plans to support [Action...
Scenario would be a long-running job that is taking too long and the user wishes to kill it and not have it restarted. If I were to send the TERM...
@rosa : I have added the documentation as discussed in #120. Let me know your feedback.
This fixes #108 and two other issues I found while working on that one: - Only try to release next unblocked job if the job actually completed, either successfully or...
First, let me apologize for dropping what is essentially a spike; I figured it was simplest to share some real code. I wanted to see how difficult it would be...
**Env and Versions:** - Ruby `3.3.0` - MySQL: `8.2.0 for macos13.5 on arm64 (Homebrew)` - MySQL Adapter: `mysql2 V0.5.5` - Rails `7.1.2` - Solid-Queue `0.1.2` **Solid_Queue Configurations:** `config/solid_queue.yml`: ```yaml development:...
We make quite a few LLM calls in our background jobs and want to leverage fibers to efficiently use the resources as these jobs spend most of their time waiting...
I am trying to override `on_thread_error` by adding the following in application.rb. ```ruby config.solid_queue.on_thread_error = ->(exception) { puts "*" * 100 puts "exception: #{exception}" # do something Rails.error.report(exception, source: "solid_queue",...
We need this feature, but I'm still not sure what it'll look like for Solid Queue. We have two use cases for it that couldn't be more different 😅 :...
It looks like some of the queries aren't compatible with a `strict_loading_by_default` configuration. With this configuration in `application.rb`, `solid_queue` doesn't work. ``` config.active_record.strict_loading_by_default = true ``` I will try to...
