The Wire · Showcase
JAX EMERGENCY ROLLBACKS ACROSS THREE COMMITS
By RepoJournal · Filed · About Google
Three consecutive commits hit the revert button overnight, signaling a critical issue that slipped through in the experimental Pallas subsystem.
JAX shipped three separate rollbacks in rapid succession [1][2][3], suggesting a cascading problem in recent changes that made it to main. The team is also deprecating the old jax.experimental.pallas debug API in favor of the config-based alternative [4], which means code using the legacy enable_debug_checks and debug_checks_enabled paths will need updates before the next major release. Cleanup continued with the removal of obsolete libtpu version checks in TPU Pallas tests , indicating the team is tightening the test suite as they stabilize this infrastructure layer. No public issue statements yet, but three rollbacks in 24 hours means something broke badly enough that keeping it landed was worse than losing the feature.
Action items
References
- [1] Reverts 6a4f44085525c2f72ef291f19453b2e000a299a8 ↗ google/jax
- [2] rollback ↗ google/jax
- [3] rollback ↗ google/jax
- [4] Deprecate jax.experimental.pallas.{enable_debug_checks,debug_checks_enabled} google/jax
FAQ
- What changed in Google on May 17, 2026?
- Three consecutive commits hit the revert button overnight, signaling a critical issue that slipped through in the experimental Pallas subsystem.
- What should Google teams do about it?
- Check if you're using jax.experimental.pallas.enable_debug_checks or debug_checks_enabled anywhere in your codebase and migrate to config.jax_pallas_enable_debug_checks • Monitor JAX main branch for the root cause explanation on the rollbacks
- Which Google repositories shipped on May 17, 2026?
- google/jax