189 wires and counting

$ follow Google

Keep up with Google in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-10-09
stories 99

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

BigQuery page-token rejection fixed, Spanner span deduplicated

By RepoJournal · Filed · About Google · Composed from the cited sources · methodology

Two client-side correctness and observability fixes in google-cloud-python lead the day, with JAX landing layout and quantile machinery on the compiler side and python-genai wiring automatic chat resumption.

fix(bigquery): drop startIndex whenever a page token is sent (#18603) googleapis/google-cloud-python

by Abhishek Acharya

RowIterator._get_next_page_response dropped startIndex from follow-up requests only when page_size was set, so a query using just max_results and start_index would send both pageToken and startIndex once the server split the result, and the API rejected it with a 400. The field is now dropped whenever a page token is sent, which unblocks paginated BigQuery reads that set an explicit start_index.

perf(spanner): eliminate redundant tracing span in run_in_transaction googleapis/google-cloud-python

by olavloite

run_in_transaction no longer emits a nested CloudSpanner.Session span alongside the outer CloudSpanner.Database one, matching the Java and Go clients, with retry, abort, and rollback events attached directly to the surviving span. Span event creation, retry delay computation, and exception stringification now sit behind span.is_recording(), so a disabled tracer costs less on the retry path.

Use unstable sort in unweighted quantile calculations. google/jax

by jax authors

When weights is None, _quantile now calls lax.sort with is_stable=False, letting XLA emit a single-op sort instead of a stable one; quantization does not depend on tie order, so only equal-comparing values such as -0.0 versus +0.0 or subnormals can come out in a different order. The change brings JAX in line with NumPy's np.quantile and np.percentile, which use an unstable partition.

Add reshape layout rule. We don't allow splitting or merging the last 2 minormost dimensions (in physical shape). Splitting on second minor dimension can be allowed in the future. google/jax

by copybara-service

The new reshape layout rule forbids splitting or merging the last two minormost dimensions in the physical shape, while any other dimension splits freely and non-adjacent merges error out rather than triggering a physical copy. Splitting on the second minor dimension may be permitted later.

feat: enable automatic continuation token resumption for chats module. googleapis/python-genai

by copybara-service

Chats now resume automatically from a continuation token instead of requiring the caller to track and replay it, with the same feature also committed under the Interactions status_update event path.

Quick answers

What shipped in Google on October 9, 2026?
Two client-side correctness and observability fixes in google-cloud-python lead the day, with JAX landing layout and quantile machinery on the compiler side and python-genai wiring automatic chat resumption. In total, 47 commits, 42 pull requests, and 10 releases landed.
Who contributed to Google on October 9, 2026?
10 developers shipped this update, including jax authors, copybara-service, Annie Luc, Google Team Member, Yvonne Yu, Abhishek Acharya, olavloite, and shradhakatyal, and 2 more.
What were the notable Google updates?
fix(bigquery): drop startIndex whenever a page token is sent (#18603), perf(spanner): eliminate redundant tracing span in run_in_transaction, and Use unstable sort in unweighted quantile calculations.