140 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-07-05
stories 5

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

JAX FIXES CRITICAL SCAN TRANSPOSE BUG THAT BROKE REF ACCUMULATORS

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

A foundational bug in JAX's scan transpose logic is fixed after the code assumed accumulators would follow a neat type-sorted pattern they never actually did.

The scan transpose implementation was making a dangerous assumption about how ref accumulators would be arranged in memory [1]. The code expected them to be sorted and contiguous by type, but real-world usage scattered them arbitrarily across the accumulator space. This created silent correctness issues that the new canonicalization logic now handles properly, complete with systematic test coverage to prevent regression [1]. In parallel, JAX is restoring cumulative sum performance on GPU by re-enabling CHLO lowering after a recent disable [2]. XLA dependencies were also bumped to the latest revision to align with upstream improvements [3].

Quick answers

What shipped in Google on July 5, 2026?
A foundational bug in JAX's scan transpose logic is fixed after the code assumed accumulators would follow a neat type-sorted pattern they never actually did. In total, 3 commits and 2 pull requests landed.
Who contributed to Google on July 5, 2026?
2 developers shipped this update, including mattjj and copybara-service[bot].
What were the notable Google updates?
[vjp3][mutable-arrays] fix scan transpose bugs with refs, [JAX] Enable CHLO lowering for cumulative sums on GPU again, and Update XLA dependency to use revision http://github.com/openxla/xla/commit/42d2e6ac6c715184ab7a64855f5162f03c561b29.