$ the-wire · showcase
JAX guards SparseCore tests behind libtpu 0.0.50 and pins a new XLA revision
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
JAX's day was test-suite plumbing and dependency pinning rather than new semantics, while google-cloud-python fixed a silently-dropped field in its storage telemetry.
Fix Windows frexp test normalization and guard SparseCore tests on older libtpu. google/jax
Six SparseCore tests now skip when libtpu is older than 0.0.50 (test_load_expanded, test_store_compressed, test_addupdate_compressed, test_write_to_transformed_ref, test_load_transformed_ref, test_scatter_add), so runs against older backends stop failing on features they don't have. The same commit normalizes e_np for non-finite inputs in testFrexpBitExact on Windows via np.isfinite(m_np).
Add pvarys on operands that are not of floating dtype even when auto_pcast is False. This is because int/bool dtypes can't be differentiated so we won't see psum on backward pass (not true for floats) google/jax
JAX now inserts pvarys on int and bool operands even with auto_pcast set to False, because those dtypes can't be differentiated and would otherwise produce no psum on the backward pass. Float operands keep the existing behavior, so this only changes what you get out of gradients through integer-typed collectives.
Update XLA dependency to use revision http://github.com/openxla/xla/commit/aff94cfcfe601e0aa07c38294a0d09b722510fcf google/jax
The pinned OpenXLA revision moves to openxla/xla commit aff94cfcfe601e0aa07c38294a0d09b722510fcf (committed 2026-09-27T06:16:56Z). JAX builds from source, check your libtpu and XLA versions match if you compile your own wheels.
fix(storage): add correct app hub uri prefix to aco traces (#18483) googleapis/google-cloud-python
The ACO telemetry emitted from the internal bucket metadata cache now carries the //storage.googleapis.com/ prefix that Cloud Trace extraction requires; the PR notes that identifiers such as projects/_/buckets/my-bucket were previously ignored, so App Hub never attributed those spans to a resource. Nothing to migrate, but traces from affected paths start landing in App Hub once you pick up the ...
Action items
