The Wire · Showcase
JAX ADDS NUMPY 2.6 TOP_K, INTEL GPU SUPPORT LANDS IN CI
By RepoJournal · Filed · About Google
JAX shipped native top_k alignment with NumPy 2.6.0 while simultaneously landing full OneAPI CI infrastructure for Intel GPU testing across the entire stack.
JAX landed two major capability expansions this cycle. First, `jax.numpy.top_k` now implements parity with NumPy v2.6.0 [2], tested against both the NumPy nightly and fallback baselines to ensure compatibility across versions. Simultaneously, OneAPI CI infrastructure hit the JAX tree [3], adding automated GPU detection, parallelization scripts, and the full test harness for Intel GPU backends. This represents the completion of GPU vendor diversity in JAX's continuous integration pipeline.
On the performance front, JAX added native support for lane dimension argmax/argmin operations with bf16 inputs on Mosaic TPU [1], enabling efficient 16-bit instruction paths via `lax.argmax/argmin` with `index_type=int16`. The team also fixed a reduce_max/reduce_min operand passthrough issue and added upstream rules for div [4] to resolve JVP call chains.
Down the stack, google-cloud-python addressed critical operational issues. A debug print statement was leaking to stdout in every BigQuery RangeQueryParameter construction [7], now removed. The team also standardized x-goog-api-client header handling to prevent duplication across the auth/core/user layers [6], reducing backend compatibility friction. Pandas-GBQ version detection gained a capability helper for safe delegation and telemetry [5], handling missing or corrupted installations gracefully.
One email a day. Unsubscribe in one click.
Keep up with Google in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Test JAX workloads against top_k for NumPy 2.6 compatibility google/jax [plan]
- → Upgrade google-cloud-bigquery immediately if using RangeQueryParameter to stop debug output googleapis/google-cloud-python [immediate]
- → Review x-goog-api-client header deduplication in your GCP client calls googleapis/google-cloud-python [monitor]
References
- [1] [Mosaic TPU] Support lane dimension argmax/argmin with bf16 input. ↗ google/jax
- [2] Add jax.numpy.top_k ↗ google/jax
- [3] [JAX:GPU][oneAPI]: Add OneAPI CI test scripts and infrastructure ↗ google/jax
- [4] Allow `reduced` operand to pass through `reduce_{max,min}`. Also add ur_rule for `div_p` since `reduce_max` jvp calls into div. ↗ google/jax
- [5] feat: add pandas-gbq capability helper ↗ googleapis/google-cloud-python
- [6] fix: deduplicate x-goog-api-client headers ↗ googleapis/google-cloud-python
- [7] fix: remove stray debug print in RangeQueryParameter constructor (#17973) googleapis/google-cloud-python