$ the-wire · showcase
JAX fixes subnormal hypot, drops Triton ragged-dot lowering
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
JAX corrected a real numerics bug in lax.hypot and a program_order transformation bug while removing an opt-in Pallas Triton ragged-dot lowering; the cloud SDKs pushed resumable uploads from generator templates all the way through google-api-core and google-auth.
[lax] Removed an opt-in Pallas Triton lowering for ragged dot google/jax
The opt-in Pallas Triton lowering for ragged dot is gone. The commit tells anyone broken by it to use Tokamax's better-supported ragged dot implementations, or plain XLA, which can lower ragged dot to cuDNN. If you depended on that lowering path, this is a breaking change.
Default float16 to non-FTZ in numerics tests and fix subnormal underflow in lax.hypot. google/jax
In lax.hypot, the power-of-two scaling exponent is now k = (nmant - minexp + 1) // 2, so squaring scaled subnormal inputs no longer underflows to zero. The same change makes numerics_test_util default input_ftz and output_ftz to False for float16, since float16 operations preserve subnormals across CPU, GPU, and TPU.
Move `program_order` to its own module and add transformation rules. google/jax
program_order moved into its own module and gained transformation rules. The bind-time exclude_mask on program_order_p had a length that changed when jvp, linearize, transpose, or dce added and removed inputs; this previously went unnoticed because program_order_p was only ever called under custom_vjp.
google-api-core: v2.41.0 googleapis/google-cloud-python
by release-please[bot]
api-core 2.41.0 adds request_body to the resumable upload constructor and support for the AsyncAuthorizedSession transport. google-auth 2.60.0 supplies the other half, adding sync credential support to AsyncAuthorizedSession, so the async upload path no longer requires a fully async credential chain.
feat: generate client, transport, and unit test templates for resumable uploads googleapis/google-cloud-python
Client, transport, and unit test templates now cover resumable upload RPCs: methods take an optional ResumableUploadConfig and return ResumableUploadSession or AsyncResumableUploadSession from google.api_core.resumable_transfer. Because resumable uploads run over HTTP, the gRPC and gRPC-async transports delegate those calls to the REST transport. Rounding out the desk: Mosaic GPU propagates HBM...