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 ROLLS BACK PALLAS TRITON CHANGES, ADDS CONFIG GUARDRAILS

By RepoJournal · Filed · About Google

JAX is partially reverting a Pallas Triton PTX compilation change while shipping new configuration controls to prevent auto-pvary insertion from breaking downstream code.

The team partially rolled forward bits needed for Pallas Triton to compile to PTX [1], but this required reverting a prior commit — the change doesn't alter existing Pallas Triton behavior, just restores compilation infrastructure. Parallel to that, JAX is shipping a new config option to disable auto-pvary insertion [2], a necessary escape hatch for teams hitting unexpected behavior from automatic parallelization. The move suggests the auto-pvary feature is too aggressive in its current state and catching real production patterns it shouldn't touch. Minor documentation fixes landed in Pallas pipelining [3], cleaning up typos in the guides. These aren't flashy changes, but they're the friction-reduction work that keeps large compute workloads from breaking between releases.

Action items

References

  1. [1] Partially rolling forward the bits needed to compile Pallas Triton to PTX ↗ google/jax
  2. [2] add config option to disable auto-pvary insertion ↗ google/jax
  3. [3] Fix typo in Pallas pipelining documentation ↗ google/jax

FAQ

What changed in Google on May 10, 2026?
JAX is partially reverting a Pallas Triton PTX compilation change while shipping new configuration controls to prevent auto-pvary insertion from breaking downstream code.
What should Google teams do about it?
Review if auto-pvary insertion is affecting your Pallas workloads — use new disable config if needed • Update to latest JAX if using Pallas Triton; Pallas changes are isolated and safe
Which Google repositories shipped on May 10, 2026?
google/jax

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.