RepoJournal
Rails @rails
114 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-31
stories 12
GitHub RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Mission Control lists failed jobs newest first, drops Rails main from CI

By RepoJournal · Filed · About Rails

rosa wintan1418 Intrepidd
3 people shipped this
rosa @rosa 6 cited wintan1418 @wintan1418 2 cited Intrepidd @Intrepidd 2 cited

The Mission Control Jobs dashboards now list failed jobs newest first, and Rails main is out of the CI matrix until a pair of controller tests are fixed.

Mission Control Jobs now orders failed executions by id desc across adapters, so the most recent failures appear on the first page [1][2]. The Solid Queue adapter uses the primary key index, and the Resque adapter reads pages from the end of its list, keeping each job's position for retry and discard operations [3]. This matches Sidekiq and GoodJob behavior and prevents important failures from being missed on later pages [1]. CI no longer runs against Rails main because two controller tests about automatically retried jobs fail there, and the team pinned resque and minitest versions for Rails 7 gemfiles to avoid boot-time NameError and ArgumentError from incompatible releases [4][5]. Meanwhile, solid_queue tests were hardened against slow databases: the pool-size worker test now gets the suite's usual budget, and lifecycle tests wait for jobs to be in flight before signaling supervisors, fixing most of the non-Rails-7.1 flakes [6][7][8]. The docs now state that retry_on cannot intercept process-death errors because the process is already gone when they are recorded [9][10].

Action items

References

  1. [1] Order SolidQueue failed executuions by id desc ↗ rails/mission_control-jobs
  2. [2] Order Solid Queue failed executions newest first ↗ rails/mission_control-jobs
  3. [3] List failed jobs newest first in the Resque adapter too ↗ rails/mission_control-jobs
  4. [4] Drop Rails main from the CI matrix for now ↗ rails/mission_control-jobs
  5. [5] Pin resque and minitest for the Rails 7 CI gemfiles ↗ rails/mission_control-jobs
  6. [6] Harden the lifecycle and pool-size worker tests against slow databases ↗ rails/solid_queue
  7. [7] Wait for jobs to be in flight before signaling supervisors in lifecycle tests ↗ rails/solid_queue
  8. [8] Give the pool-size worker test the suite's usual budget ↗ rails/solid_queue
  9. [9] Document that retry_on can't intercept process-death errors ↗ rails/solid_queue
  10. [10] Document that retry_on can't intercept process-death errors ↗ rails/solid_queue

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

the week in review Rails moves config to class attributes the month in review Rails deepens Ractor safety, ships Marcel 2.0, and retires decade-old APIs
Topics: Ruby Full archive →

Quick answers

What shipped in Rails on August 31, 2026?
The Mission Control Jobs dashboards now list failed jobs newest first, and Rails main is out of the CI matrix until a pair of controller tests are fixed. In total, 8 commits and 4 pull requests landed.
Who contributed to Rails on August 31, 2026?
3 developers shipped this update, including rosa, wintan1418, and Intrepidd.
What were the notable Rails updates?
Order SolidQueue failed executuions by id desc, Order Solid Queue failed executions newest first, and List failed jobs newest first in the Resque adapter too.
♥

$ log @rails --recent

ActionDispatch drops regexp re-serialization per ParameterFilter build 3 shipped Rails fixes docker-entrypoint to honor extra server flags 8 shipped Layouts guide rewritten, Bootsnap 1.26.0 fixes cache corruption 35 shipped PostgreSQL triggers stay disabled after failed yield 23 shipped

$ log --all # elsewhere on the wire

Meta React Native adds Stable API guards to renderer attributed string FastAPI & Pydantic Pydantic fixes Mypy plugin crash, tightens datetime constraints

$ ls showcases/

Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic OpenAI

$ 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.