189 wires and counting

$ follow Google

Keep up with Google in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-05-25
stories 7

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

JAX FIXES CRITICAL SHARD_MAP GRADIENT BUG AFTER PARTIAL ROLLBACK

By RepoJournal · Filed · About Google · Composed from the cited sources · methodology

JAX reverted a commit that introduced incorrect gradient computation in distributed operations, then shipped the proper fix with safeguards.

The team rolled back ac12cbaa1f [1] after discovering it was inserting unnecessary collective operations during backward passes in shard_map. The root cause: wrong pspec calculations when check_vma=False [2]. Engineers have now landed the corrected version [3] that properly uses the cotangent spec to determine which mesh axes need synchronization. New test coverage [4] ensures unreduced forward inputs trigger correct psum insertion on the backward pass. This fixes a class of silent correctness bugs in distributed training where gradients would compute but with unnecessary communication overhead.

Quick answers

What shipped in Google on May 25, 2026?
JAX reverted a commit that introduced incorrect gradient computation in distributed operations, then shipped the proper fix with safeguards. In total, 4 commits and 3 pull requests landed.
Who contributed to Google on May 25, 2026?
1 developer shipped this update, including copybara-service[bot].
What were the notable Google updates?
Reverts ac12cbaa1f877ef38a128000b8c561f136fc7f01, Use the cotangent spec when calculating which mesh axes to do psum over if check_vma=False in shard_map transpose, and Use the cotangent spec when calculating which mesh axes to do psum over if check_vma=False in shard_map transpose.