The Wire · Showcase
JAX SHIPS STABLE SORT KNOB, GOOGLE CLOUD AUTH STRIPS PYOPENSSL
By RepoJournal · Filed · About Google
JAX's top_k now lets you trade sort stability for speed, while google-cloud-python rips out pyOpenSSL for native crypto in the biggest auth overhaul this quarter.
JAX landed a performance lever on jax.lax.top_k [1] with a new is_stable flag defaulting to True, letting users opt into faster unstable sorts when tie-breaking order doesn't matter. That's paired with heavyweight GPU work: Mosaic GPU now handles MXFP4 matrix multiply at block_size=16 [3], unlocking Blackwell hardware capabilities that were previously locked to block_size=32, and Pallas reapplied critical missing code [2] from a prior GPU device handling refactor. google-cloud-python shipped a security-first auth rewrite [5] yanking pyOpenSSL entirely in favor of standard library ssl and cryptography, plus it bakes in RAM-only key handling via Linux memfd_create to keep secrets off disk entirely. The same auth module now catches PermissionErrors on workload certificate reads [6] instead of hanging for 30 seconds in sandboxed environments like snap packages. JAX also reorganized flattree internals [4] to make unpacking and filtering commute, a necessary fix for scan JVP operations that filter tangent zeros.
Action items
- → Audit your jax.lax.top_k calls - benchmark against is_stable=False if sort order variance is tolerable google/jax [plan]
- → Plan google-cloud-python auth upgrade before next service deploy - pyOpenSSL removal is breaking googleapis/google-cloud-python [plan]
- → Test workload auth in sandboxed environments after upgrading - PermissionError handling prevents startup hangs googleapis/google-cloud-python [monitor]
References
- [1] Add is_stable flag to jax.lax.top_k google/jax
- [2] [Pallas][Triton] Reapply the missing code from "Added gpu_info and removed gpu device fallback from pallas_call_lowering" PR google/jax
- [3] [Mosaic GPU] Add support for MXFP4 MMA with block_size=16 ↗ google/jax
- [4] Reorganize flattree implementation. ↗ google/jax
- [5] refactor(auth): replace pyOpenSSL with standard ssl and cryptography ↗ googleapis/google-cloud-python
- [6] fix(auth): handle PermissionError on workload certificates to avoid startup hang and crash ↗ googleapis/google-cloud-python
FAQ
- What changed in Google on July 3, 2026?
- JAX's top_k now lets you trade sort stability for speed, while google-cloud-python rips out pyOpenSSL for native crypto in the biggest auth overhaul this quarter.
- What should Google teams do about it?
- Audit your jax.lax.top_k calls - benchmark against is_stable=False if sort order variance is tolerable • Plan google-cloud-python auth upgrade before next service deploy - pyOpenSSL removal is breaking • Test workload auth in sandboxed environments after upgrading - PermissionError handling prevents startup hangs
- Which Google repositories shipped on July 3, 2026?
- google/jax, googleapis/google-cloud-python