RepoJournal
Google

Google

JAX, the GenAI SDK, and the Cloud libs — Google's open source layer

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Mon 18 may
  16. Tue 19 may
  17. Wed 20 may
  18. Thu 21 may
  19. Sat 23 may
  20. Sun 24 may
  21. Mon 25 may
  22. Tue 26 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

JAX TIGHTENS SEGMENT SHARDING RULES WHILE PALLAS FIXES CRITICAL TPU HANGS

By RepoJournal · Filed · About Google

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

FAQ

What changed 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.
What should Google teams do about it?
Audit your JAX segment_sum/max/min/prod calls for conflicting sharding specs before next release • Upgrade python-genai to v2.7.0 if using Vertex computer_use or CSV document processing • Update local Kokoro configuration references if you maintain google-cloud-python forks
Which Google repositories shipped on May 29, 2026?
google/jax, googleapis/python-genai, googleapis/google-cloud-python

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.