[dependabot]

Bumps solid_queue from 1.7.0 to 1.7.2.

Release notes

Sourced from solid_queue's releases.

v1.7.2

Summary

Concurrency-limited jobs now give their slot back only to the semaphore they got it from. That fixes a job that ran past its duration letting an extra job run alongside the next holder (#827). It also fixes jobs whose class goes missing during a deploy giving back a slot they never took, or keeping one they did take. Nothing needs migrating; see "Upgrading to version 1.7.2" for what to do before 2.0.

What's Changed

• Give concurrency slots back only to the semaphore they came from by @​rosa in rails/solid_queue#831

Full Changelog: rails/solid_queue@v1.7.1...v1.7.2

v1.7.1

Summary of changes

Process resilience

• Processes stop and get replaced when their heartbeats keep failing past the alive threshold (#778).
• The async supervisor replaces dead threads even if releasing their jobs fails during a database outage (#791, fixes #823).
• Workers stop when finishing a job fails (#768).
• Forked processes exit immediately, which avoids the exit hang on SQLite (#801).
• The Puma plugin keeps shutting down when its output pipe is gone (#800, #737).
• In async mode, in-flight jobs go back to the queue when shutdown times out (#815).

Jobs and concurrency

• Jobs whose class no longer loads are failed with ClassMissingError instead of being dropped (#783).
• Discarding ready jobs in bulk unblocks the jobs waiting behind them (#818).
• Retrying failed jobs in bulk resets their retry counters (#817).
• Concurrency locks are taken in key order when dispatching several jobs, which avoids deadlocks (#812).
• One less query per enqueue (#819).
• On MySQL, failed jobs with very large error messages no longer crash workers (#822).
• Bulk-discarding claimed executions raises UndiscardableError instead of NameError (#828).
• Batch completion errors no longer block the next job (#816).

Queues and recurring tasks

• Queue prefixes escape _ and %, and each queue is selected only once (#811).
• Dynamic tasks recreated with the same key are rescheduled (#793).

Other

• The CLI is no longer eager loaded (#826).
• CI pins json below 3 for Rails 7.1 and 8.0 (#813). That's test-only, but it explains the Gemfile change.
• README additions: READ COMMITTED for MySQL, sql_notifications, the Puma plugin's behavior, retry_on and process death, async mode with TERM and QUIT, and removing leftover recurring tasks.

What's Changed

• Replace terminated threads even if releasing their claimed jobs fails by @​rosa in rails/solid_queue#791
• Stop processes whose heartbeats keep failing past the alive threshold by @​wintan1418 in rails/solid_queue#778
• Stop workers when job finalization fails by @​rafael-pissardo in rails/solid_queue#768
• Add README notes on READ COMMITTED, sql_notifications, and the Puma plugin's failure behaviour by @​rosa in rails/solid_queue#795
• Assert the successful job's output regardless of execution order by @​rosa in rails/solid_queue#796
• Document that retry_on can't intercept process-death errors by @​wintan1418 in rails/solid_queue#789
• Harden the lifecycle and pool-size worker tests against slow databases by @​rosa in rails/solid_queue#798
• Exit forked processes immediately to avoid a SQLite mutex deadlock at exit by @​rosa in rails/solid_queue#801

... (truncated)

Commits

• b9c646a Bump solid_queue to 1.7.2
• 8b2a87b Let the job answer for the concurrency slot it holds
• 310496a Test that a job records the semaphore it created on MySQL, and correct the up...
• 6af5101 Place the semaphore note under 1.7.2 in UPGRADING
• 50ca656 Read the acquired semaphore with a lock, and record the limit used
• 62c2927 Give concurrency slots back only to the semaphore they came from
• 24d936a Bump solid_queue to 1.7.1
• 3d7c5d0 Keep batch completion errors from blocking subsequent jobs
• 7323f03 Move the concurrent dispatching test next to the other semaphore lock tests
• a034856 Acquire concurrency locks by key when dispatching several jobs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)