$ the-wire · showcase
JAX ships tracing-time ordering, xla dependency bump
By RepoJournal · Filed · About Google
JAX landed a quiet but meaningful reliability fix this period: program order now sticks even when exclude_argnames is passed as None, plus an XLA dependency roll.
JAX landed a quiet but meaningful reliability fix [1] that makes tracing respect program order even when exclude_argnames is None. The internal commit [2] carries the same change plus a PiperOrigin-RevId, so the two share the same intent. Alongside it, the team reverted a prior commit twice [3][4], signaling instability in the change being rolled back. The XLA dependency moved to a new revision [5], pinning the tree to upstream commit 69325769ed5c4191b16e7f5fd37d5d5ea114a18d. This is routine maintenance: nothing here breaks existing code, but the ordering change could affect tracing semantics in edge cases where exclude_argnames is None. Watch the revert activity if you depend on the feature being recalled.
Action items
- → Review the program_order_p change if you rely on exclude_argnames being None google/jax [monitor]
- → Track the revert of 2610691a3 for stability implications google/jax [monitor]
References
- [1] Use program_order_p even if exclude_argnames is None ↗ google/jax
- [2] Use program_order_p even if exclude_argnames is None ↗ google/jax
- [3] Reverts 2610691a3fcfc16d5fd09e714f492f518978622c ↗ google/jax
- [4] Reverts 2610691a3fcfc16d5fd09e714f492f518978622c ↗ google/jax
- [5] Update XLA dependency to use revision http://github.com/openxla/xla/commit/69325769ed5c4191b16e7f5fd37d5d5ea114a18d ↗ google/jax