$ the-wire · showcase
JAX preps jaxlib for the stable ABI, Spanner metrics interceptor miscounted
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
JAX's C++ layer steps toward Python's limited API, cuDNN SDPA flex attention returns behind an arch>=90 guard, and two Spanner fixes split the day: metrics that were silently dropped and a test suite that got 55% faster.
Replace `PyTuple_SET_ITEM` and `PyList_SET_ITEM` with nanobind builders. google/jax
Raw PyTuple_SET_ITEM and PyList_SET_ITEM calls are out of jaxlib and xla/python, replaced by nanobind tuple_builder and list_builder (plus nb::detail::seq_builder<false> in type_caster<absl::Span<T const>>::from_cpp), because those macros are not part of the Python Stable ABI. This is groundwork for building against Py_LIMITED_API, not a behavior change for users today.
Enable cuDNN SDPA flex attention google/jax
cuDNN SDPA flex attention is reenabled after the earlier revert, now gated on architectures >= 90, so Hopper and newer get the path back and older cards skip it. NVIDIA authored the change, which matters if you benchmarked flex attention on those accelerators and saw the fast path disappear.
fix(spanner): correctly wrap async streaming calls in metrics interceptor googleapis/google-cloud-python
Async streaming RPCs like ExecuteStreamingSql were being wrapped in _AsyncUnaryResponseWrapper instead of _AsyncStreamingResponseWrapper, so their metrics never recorded. The cause: grpc.aio streaming call objects expose __aiter__ but no __anext__, and AsyncMetricsInterceptor's hasattr(response, "__anext__") check therefore missed every one of them. If you rely on client-side Spanner metrics, s...
test(spanner): speed up unit test suite and eliminate idle retry sleeps googleapis/google-cloud-python
Spanner's unit suite drops from roughly 66s to 29s, about 55% faster, by mocking the localized time.sleep and asyncio.sleep in transaction, snapshot, and batch commit retry tests so backoff no longer idles in wall clock, and by skipping live gRPC transport setup. Retry counts and delay values are still asserted; only the waiting is gone.
[CI] Restrict `google-benchmark` to `python_version<"3.14"` in `build/test-requirements.txt`. google/jax
google-benchmark==1.9.5 publishes only cp312-abi3 wheels and sets py_limited_api="cp312" in its sdist, which cannot build on free-threaded Python 3.14t or 3.15t where Py_LIMITED_API conflicts with Py_GIL_DISABLED. JAX pins it to python_version<"3.14" in build/test-requirements.txt and pulls it from the 3.14+ lockfiles, so only JAX's own CI environments are affected. The remaining items today ar...