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-29
stories 57

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

JAX TIGHTENS SEGMENT SHARDING RULES WHILE PALLAS FIXES CRITICAL TPU HANGS

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

JAX is cracking down on conflicting sharding specifications in segment operations while simultaneously shipping a critical fix that prevents TPU Interpret Mode from deadlocking when simulated devices fail.

The JAX team shipped two major enforcement changes to segment operations that will break existing code if you're mixing unreduced and reduced sharding directives [1] [2]. Segment sum, max, min, and prod now validate that you're not simultaneously using both parameter specs and unreduced/reduced output sharding, a pattern that was silently producing incorrect results. This is a hard requirement before the next major version lands. More critically, Pallas TPU Interpret Mode now properly handles device failures [3], implementing failure tracking and propagation so that when one simulated device crashes, others fail cleanly instead of hanging forever waiting for signals that will never arrive. The fix includes test cases that deadlock without it. Over in python-genai, the team shipped v2.7.0 [4] with computer_use field support for Vertex and CSV document mime type support for the Interaction API [5]. On the infrastructure side, google-cloud-python is consolidating CI/CD by moving prerelease and core_deps tests from GitHub Actions to Kokoro [6] [7], removing hardcoded package lists that were causing test coverage gaps [8].

Action items

References

  1. [1] Error out if `*pspec` or `pspec[...]` is used when unreduced/reduced is non-empty ↗ google/jax
  2. [2] Add out_sharding to segment_{sum,max,min,prod}. Only allow unreduced out_sharding to `segment_sum`. ↗ google/jax
  3. [3] [Pallas] Improve error handling in TPU Interpret Mode to avoid hangs. ↗ google/jax
  4. [4] v2.7.0 ↗ googleapis/python-genai
  5. [5] docs: update the docs for 2.7 ↗ googleapis/python-genai
  6. [6] chore: update kokoro prerelease and core_deps jobs (#17286) ↗ googleapis/google-cloud-python
  7. [7] chore: remove prerelease and core_deps from GHA (#17291) ↗ googleapis/google-cloud-python
  8. [8] tests: remove hardcoded packages in system.sh (#17301) ↗ googleapis/google-cloud-python

Quick answers

What shipped in Google on May 29, 2026?
JAX is cracking down on conflicting sharding specifications in segment operations while simultaneously shipping a critical fix that prevents TPU Interpret Mode from deadlocking when simulated devices fail. In total, 29 commits, 25 pull requests, and 3 releases landed.
Who contributed to Google on May 29, 2026?
1 developer shipped this update, including copybara-service[bot].
What were the notable Google updates?
Error out if `*pspec` or `pspec[...]` is used when unreduced/reduced is non-empty, Add out_sharding to segment_{sum,max,min,prod}. Only allow unreduced out_sharding to `segment_sum`, and [Pallas] Improve error handling in TPU Interpret Mode to avoid hangs.