[dependabot]

Bumps solid_queue from 1.3.1 to 1.7.0.

Release notes

Sourced from solid_queue's releases.

v1.7.0 - batches

This is a big one! Solid Queue finally supports job batches thanks to @​jpcamara. Check the README for more details about how to use these. This took ages despite being a very requested feature 😅 Big thanks to @​jpcamara for his patience, refinements and production-app tests!

What's Changed

• Clarify that concurrency + bulk enqueuing is a perf caveat, not unsafe by @​Gnirt in rails/solid_queue#785
• Wait for polling queries in logging tests instead of sleeping by @​wintan1418 in rails/solid_queue#775
• Keep semaphore slots held while blocked jobs are enqueued in concurrency test by @​wintan1418 in rails/solid_queue#776
• Give in-flight jobs enough pause to survive slow shutdowns in tests by @​wintan1418 in rails/solid_queue#782
• Include the error in fail_many_claimed events and document recovery by @​wintan1418 in rails/solid_queue#779
• Replace terminated forks even if releasing their claimed jobs fails by @​wintan1418 in rails/solid_queue#781
• Honour TERM received during supervisor boot before forking workers by @​rafael-pissardo in rails/solid_queue#770
• Batch Support by @​jpcamara in rails/solid_queue#142

New Contributors

• @​Gnirt made their first contribution in rails/solid_queue#785

Full Changelog: rails/solid_queue@v1.6.0...v1.7.0

v1.6.0 - fiber execution mode (with Async)

A long-awaited feature thanks to @​crmne on this release: instead of using a thread pool to run jobs in multiple threads per works, you can now use fibers on a single fiber reactor thread. To use this, you just need to specify the number of fibers instead of the number of threads in your worker configuration, like this:

workers:
  - queues: "api*"
    fibers: 100
    polling_interval: 0.05

It uses Async under the hood, so you need to have that as a dependency for it to work. Also, you need to be using fiber isolation in Rails (config.active_support.isolation_level`` = :fiber).

This can be very useful for I/O-bound workloads, such as those involving LLM calls.

What's Changed

• Add fiber worker execution mode by @​crmne in rails/solid_queue#728
• Roll back transactions leaked by killed job threads in tests by @​rosa in rails/solid_queue#773
• Document how to update dynamic recurring tasks by @​wintan1418 in rails/solid_queue#777

New Contributors

• @​crmne made their first contribution in rails/solid_queue#728
• @​wintan1418 made their first contribution in rails/solid_queue#777

Full Changelog: rails/solid_queue@v1.5.1...v1.6.0

v1.5.1

What's Changed

• Fix flaky tests caused by leaked job threads and signal timing by @​rosa in rails/solid_queue#766
• Add an update generator to copy new migrations by @​rosa in rails/solid_queue#765
• Wait for the continuable job to start before interrupting it by @​rosa in rails/solid_queue#767
• Add --only-recurring to run just the recurring scheduler by @​rafael-pissardo in rails/solid_queue#757
• Use with_connection in DistinctValues by @​trevorturk in rails/solid_queue#769
• Replace forked processes that fail to boot by @​sapandiwakar in rails/solid_queue#760

... (truncated)

Commits

• e2b5384 Bump solid_queue to 1.7.0
• 5352228 Reset pooled connections when flipping the batches schema in tests
• 112bb1c Refine batch support after a full review
• 1bcac83 Add batch support
• fcb5f7a Name the supervisor's stop checkpoint and simplify its lifecycle
• 124176a Honour TERM received during supervisor boot before forking workers
• 174cb07 Protect the shutdown reap from release failures too
• 0526401 Replace terminated forks even if releasing their claimed jobs fails
• 6816e52 Include the error in fail_many_claimed events and document recovery
• fc5fb59 Wait longer for the supervisor to fail the killed worker's job
• 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)

[developerz-ai]

Needs a human: dinndev2/adminer #32: a check keeps ending without a result and needs a look at CI.

A check on this pull request ended without a result on the code (GitHub cancelled it, marked it stale, or the job failed before running a single step) and a re-run did not settle it: it ended the same way again, GitHub refused the re-run (this installation has not accepted the app's Actions write permission, the run is too old to re-run, or the repo forbids it), the job's workflow run was still going past the CI wait ceiling, so GitHub would not re-run the job yet, or it is not a job the platform can re-run. Such a job never reported on the code, so no fix was attempted and nothing was split. Look at the CI configuration (a job timeout, a concurrency group, runner availability, the workflow permissions). If GitHub refused the re-run, re-run the job by hand or push a commit; if the job's workflow run was still going, the job is re-runnable once that run finishes, and a re-run by hand would be refused the same way.

🤖 Posted by developerz.ai — an automated agent, not a human.