RepoJournal
Rails @rails
159 wires and counting

$ follow Rails

Keep up with Rails in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-24
stories 10
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Solid Queue workers now die on finalization failure to free stuck claims

By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology

Ryuta Kamizono rafael-pissardo Rosa Gutierrez 55728
4 people shipped this
Ryuta Kamizono @kamipo 3 cited rafael-pissardo @rafael-pissardo 1 cited Rosa Gutierrez @rosa 1 cited 55728 @55728

Solid Queue just shipped a fix that stops claimed executions from hanging forever after transient database errors, by killing the owning worker.

Solid Queue's new behavior [1] wraps finalization failures into a dedicated error and stops the owning worker so shutdown releases the claim for retry. This directly fixes a class of stuck jobs that could previously linger after transient DB errors, and the fix is paired with a scope-tightening follow-up [2] that avoids the redundant still-claimed check on every ordinary failure. As the PR summary puts it, "Prevent claimed executions from remaining stuck after transient database errors by terminating the owning worker so shutdown releases the claim." [3] Meanwhile, Rails itself is mostly quiet: a small MySQL reader fix [4] ensures `indexes([])` returns early instead of opening a connection to read nothing, and two documentation corrections [5][6] tidy up the Store dirty tracking example and the AVG return type. Ryuta Kamizono also merged a separate PR that backs the MySQL `fetch_indexes` change, all part of a light 6-commit, 4-PR day across the stack.

Action items

References

  1. [1] Stop workers when job finalization fails ↗ rails/solid_queue
  2. [2] Scope the finalization guard and restore perform's shape ↗ rails/solid_queue
  3. [3] Stop workers when job finalization fails ↗ rails/solid_queue
  4. [4] Don't touch the connection in MySQL's `fetch_indexes` for an empty list ↗ rails/rails
  5. [5] Merge pull request #58539 from 55728/fix-store-dirty-tracking-doc-example ↗ rails/rails
  6. [6] Merge pull request #58538 from 55728/fix-calculations-avg-doc-return-type ↗ rails/rails

$ ls rails/reviews/ # the step-back reads

the week in review Ractor-ready Active Record and Active Job land in Rails the month in review Herb becomes Rails 8.2 default
Full archive → Weekly reviews →

Quick answers

What shipped in Rails on August 24, 2026?
Solid Queue just shipped a fix that stops claimed executions from hanging forever after transient database errors, by killing the owning worker. In total, 6 commits and 4 pull requests landed.
Who contributed to Rails on August 24, 2026?
4 developers shipped this update, including Ryuta Kamizono, 55728, rafael-pissardo, and Rosa Gutierrez.
What were the notable Rails updates?
Stop workers when job finalization fails, Scope the finalization guard and restore perform's shape, and Stop workers when job finalization fails.
♥

$ log @rails --recent

Attribute-read regression fixed, decimal numericality corrected 79 shipped in_order_of double-serializes values, id_value alias restored 50 shipped Inlined attribute writers, leaner ActiveRecord::Key 31 shipped MySQL 5.6 falls off the support floor as Arel stops rebuilding literals 27 shipped

$ log --all # elsewhere on the wire

Alignment & Post-training verl standardizes low-precision rollout kernels on DeepGEMM Agent Security Guardrails exposes hooks over HTTP, certifi floor raised in agent-scan

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.