$ the-wire · showcase
RAILS PATCHES THREE SUBTLE BUGS THAT BREAK REAL WORLD CODE
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
In_order_of was silently dropping nil values even when you explicitly named them, and Arel stopped working standalone after ActiveSupport changes.
Rails merged three fixes overnight that each solve production problems hiding in plain sight. The headline issue: Enumerable#in_order_of with default filter: true was dropping nil elements even when nil was explicitly in your series, breaking any code that relied on nil as a meaningful value [1]. That's now fixed and consistent with filter: false behavior. Meanwhile, Arel stopped being requireable on its own because it references ActiveSupport::Ractors internally [2], causing NameError in libraries that pull Arel directly. That's been resolved. The third fix makes Cache#exist? instrumentation actually include the call options in its payload [3], so you can finally debug cache behavior without losing context. None of these are flashy, but all three are the kind of fixes that cause hours of debugging when they hit production.
Action items
- → Pull the latest main if you use in_order_of with nil values rails/rails [plan]
- → Update if Arel requiring fails in your library stack rails/rails [immediate]
- → Monitor next release notes for these in the changelog rails/rails [monitor]
References
- [1] Keep nil elements named in the series for in_order_of rails/rails ↗
- [2] Allow Arel to be required on its own rails/rails ↗
- [3] Merge pull request #57915 from 55728/fix-cache-exist-instrument-options rails/rails ↗
