$ the-wire · showcase
JAX lets reshape propagate through collectives
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
JAX's explicit-sharding reshape rule now handles axis merges that need cross-device communication instead of raising NotImplementedError, and lax.map drops auto_axes when batch_size is given.
Support collectives in the reshape partitioning rule. google/jax
The `_reshape_collective_rule` used to raise `NotImplementedError` whenever a reshape required collectives or carried an `out_sharding` that zero-communication propagation could not produce. It now builds a reshard plan and reuses the reshard partitioning logic, so merges like `f32[4@x, 4@y] -> f32[16@(x, y)]` propagate instead of failing.
Remove `auto_axes` from `lax.map` when `batch_size` is specified. google/jax
Passing `batch_size` to `lax.map` no longer accepts `auto_axes`, removing the ambiguity between the two ways of specifying batch layout. Code that sets both will need to pick one.
Update XLA dependency to use revision http://github.com/openxla/xla/commit/ce107528b122ec3ac3ae9ed35b5cdd0813e6b61c google/jax
JAX's pinned OpenXLA revision moves to `ce107528b122`, committed 2026-11-06, so anything building JAX from source will pull a newer XLA.
Support collectives in the reshape partitioning rule. google/jax
The same reshape-collective work landed through the mirrored copybara path, confirming the change is present in both the jax-ml and google/jax trees.
Action items
- → Drop `auto_axes` from any `lax.map` call that also passes `batch_size` google/jax [plan]