$ the-wire · showcase
RAILS FIXES SILENT ROUTING FAILURES AND DATABASE LEAK CONDITIONS
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
1 person shipped this
Rails shipped two critical fixes overnight that address a routing bug silencing boolean options and an async database maintenance leak that could corrupt test suites.
The routing fix [1] corrects a long-standing issue where falsy values like `format: false` and `anchor: false` passed through the deprecated positional-hash form were dropped entirely without warning, producing routes that behaved differently than their keyword-form equivalents. This wasn't just a deprecation miss; it was a silent correctness failure that could change application behavior during upgrades. The second fix [2] tackles a database connection leak in async executor scenarios where maintenance work was queued under lock but never properly awaited, causing the leak checker to miss outstanding checkouts and corrupt subsequent tests. Both landed as targeted patches to the main rail, not version bumps. On the CI side, the buildkite-config team wrapped docker compose operations with automatic retries [3] and upgraded to Docker Compose v2 across the board [4], addressing intermittent image pull timeouts that were flaking test runs.
Action items
- → Review routes using deprecated positional-hash format with boolean options rails/rails [plan]
- → Pull latest rails/rails if running async executor in test suite rails/rails [monitor]
- → Verify Docker Compose v2 readiness in CI if running custom buildkite config rails/buildkite-config [monitor]
References
- [1] Honor falsy values in routing's deprecated positional-hash options ↗ rails/rails
- [2] Wait for any asynchronous connection maintenance work before leak check ↗ rails/rails
- [3] Separately pull compose dependencies so they can be retried ↗ rails/buildkite-config
- [4] Use Docker Compose v2 everywhere ↗ rails/buildkite-config
