$ the-wire · showcase
google-auth 2.62.1 fixes SigV4 signing against STS FIPS endpoints
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
JAX adds exact sinpi/cospi/tanpi while python-genai stops silently dropping unknown request fields, but today's only must-act is a google-auth patch for AWS FIPS region endpoints.
fix(auth): strip -fips suffix from AWS service name in SigV4 signing (#18920) googleapis/google-cloud-python
In google-auth 2.62.1, SigV4 signing against regional FIPS STS endpoints (sts-fips.{region}.amazonaws.com) now derives the canonical service name by stripping the -fips suffix; previously _generate_authentication_header_map used host.split(".")[0], producing sts-fips in the credential scope while the Host header must stay sts-fips.{region}.amazonaws.com. If you call AWS STS through FIPS endpoin...
Add jax.lax.sinpi, cospi, and tanpi. google/jax
jax.lax.sinpi, jax.lax.cospi, and jax.lax.tanpi reduce x modulo 2 before multiplying by pi, so integer and half-integer inputs return exact values instead of the small nonzero residue that jnp.sin(jnp.pi * x) produces from rounding pi first. Large inputs stop losing accuracy; the PR notes sin(pi) as the canonical case.
fix: preserve unknown fields and open-union variants in Interactions models googleapis/python-genai
The Python SDK now keeps unknown fields at every nesting level in both responses and requests, so unrecognized request fields are forwarded to the API rather than silently dropped. The consequence is a behavior change: unsupported options such as transcription_config.diarization are now rejected by the server instead of being ignored, which is exactly the failure mode the linked issue reported.
[partitioning] Add `p{max,min}_scatter` and lower `reduce_{max,min}` scatters. google/jax
New internal pmax_scatter and pmin_scatter collectives in lax.parallel lower to stablehlo.reduce_scatter, wired into the explicit shard_map rules for reduce_max and reduce_min. These are internal primitives, but they give shard_map real lowering for the two reductions instead of whatever it did before.
[pallas:triton] Removed the previously deprecated ops google/jax
The previously deprecated Pallas Triton ops are gone, so any kernel still importing them stops working at the next JAX upgrade. Worth a grep before you pin a newer version.
Support 64-bit integer BLAS and LAPACK when JAX is linked directly against LAPACK. google/jax
Building with -DJAX_LAPACK_ILP64 lets lapack_kernels_using_lapack.cc bind the 64-bit (_64_) BLAS and LAPACK symbols, with JAX_LAPACK_FUNC_SUFFIX as an override; lu_solve and testScipyQrModes now cast pivot arrays to int32 to match. This matters only if you link JAX directly against an ILP64 LAPACK and run jax_enable_x64=True.
perf(spanner): optimize request ID header generation and retry closures googleapis/google-cloud-python
Elsewhere, the Spanner client pre-formats its process request-ID prefix at import and caches per-database prefixes in instance.__dict__, and google-auth 2.62.1 also switches mTLS certificate rotation to an unencrypted key.
Action items
- → Upgrade google-auth to 2.62.1 if you sign AWS STS requests against regional FIPS endpoints googleapis/google-cloud-python [plan]