Ruby on Rails: Getting Rails Ready for Ractors

A cluster of merged pull requests made callbacks, URL helpers, and model conversion logic safe to run inside Ractors, while a separate pair of fixes hardened Active Record's test suite against unpredictable SQL ordering.

Duration: PT2M35S

Episode overview

This episode is a short developer briefing from Ruby on Rails.

It explains recent repository work in plain language.

  • Show: Ruby on Rails
  • Published: 2026-08-21T13:14:39Z
  • Audio duration: PT2M35S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning. It's August 21st, and today's Rails activity centers on one big push: making core framework pieces safe to run inside Ractors.

The headline theme is Ractor compatibility. Three merged pull requests worked together on this. PR 58522 fixed callbacks so they're only made shareable in raise mode, and along the way fixed a bug where freeze was incorrectly marked as a protected method. Then Edouard-chin landed two companion pull requests, 58529…

The second theme is test reliability in Active Record. viralpraxis landed two related fixes, PR 58527 and PR 58528, removing tests that quietly depended on database-specific, unspecified select ordering. SQLite, MySQL, and Trilogy happened to return rows in an order that Postgres didn't guarantee, and a companion…

One more item worth flagging: PR 58532, still open, proposes indexing view directories instead of globbing per template lookup, targeting what's described as squared-cost directory reads at scale. Worth watching once it lands.

What's next: if you're working with Ractors, expect more of these piecemeal compatibility fixes as remaining isolation errors surface. And if your Active Record tests assume row order, the new SQLite…

Th…

Nearby episodes from Ruby on Rails

  1. Documentation Cleanup and Quiet Correctness Fixes
  2. Weekly Recap - Ractor Safety and Data Correctness
  3. Trimming the Fat in Reflection Code
  4. Lazy Loading and Doc Corrections
  5. Ractor-Ready and Batching Up
  6. Consistency Fixes and Ractor Readiness
  7. Association Integrity Fixes Take Center Stage
  8. Batching the Schema Reader, Closing Scope Leaks