$ the-wire · showcase
JAX splits Mosaic debug info to fix cache key mismatch; python-genai regenerates GAOS SDKs
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
JAX untangles a cache-key versus executable-fingerprint discrepancy in Mosaic TPU debug locations, while the Python client libraries line up Python 3.15 support and a new Firestore decimal type.
[Mosaic TPU] Separate debug info from the Mosaic kernel `body` into a new `debug_locations` in `custom_call_config` with a new configuration flag `jax_mosaic_unzip_debug_locations`. google/jax
Mosaic TPU debug info moves out of the kernel body into a new debug_locations field in custom_call_config, gated by the jax_mosaic_unzip_debug_locations flag. The pull request states this resolves a discrepancy between JAX compilation cache key generation and XLA executable fingerprint generation: two kernels differing only in source location or function name used to produce identical JAX cache...
feat(firestore): add BSONDecimal128 support googleapis/google-cloud-python
Firestore gains a BSONDecimal128 container class at google.cloud.firestore_v1.bson for lossless 128-bit decimal storage, constructed from str, int, float, decimal.Decimal, or an existing BSONDecimal128 instance, per the pull request. It arrives with a .to_dec helper.
feat: add Python 3.15 support to handwritten libraries (#18452) googleapis/google-cloud-python
Handwritten and veneer libraries now carry the Python 3.15 classifier, and this change strips out several test work-arounds. Packages depending on pyarrow are flagged as needing a follow-up update from the maintainer.
chore(crc32c): run manylinux wheel validation and upload in isolated Python 3.12 venv (#18453) googleapis/google-cloud-python
The google-crc32c manylinux wheel pipeline now validates and uploads inside an isolated Python 3.12 venv, and drops the flaky ppa:deadsnakes/ppa install that build.sh used to run on the Ubuntu 20.04 host before launching the manylinux2014 container. Two Kokoro linux_wheel failures prompted the rework.
Dynamically derive TPU process count and bounds in multiprocess tests google/jax
TPU multiprocess tests stop hardcoding --num_processes=4 and derive the count from available physical chips and tpu_chips_per_process, with TPU topology logic pulled into _get_tpu_bounds. Chip configurations of 1, 2, 4, and 8 are now covered across v4, v5p, v5e, v6e, tpu7x, tpu8i, and tpu8t.
