Daily Engineering Intelligence

Technology Newspaper

← Back to Home

Engineering Intelligence β€” Sunday

October 11, 2026

πŸ”₯ What Changed

Honest quiet Sunday after a dense Fri/Sat. No Tier-1 primary shipped in the 10-09…11 window that clears the WC bar.

Go holds unchanged: #82026 CL 846325 still NEW (unmerged); #81957 Pratt CL 847406 still NEW under review; #81759 open; #81864 tip-merged 10-07 (container-aware GOMAXPROCS vs nsfs mountinfo) β€” tip-only, no backport/release yet. Azure PIR finals 7Q30-010 / 7QL5-Z50 still preliminary (expect ~10-13/14). grpc-go v1.85 not released (latest stable v1.84.0; due ~10-13).

One Worth Your Time: golang/go#82120 β€” x/net/http2.Transport permanently leaks connection-level flow control when RoundTrip errors after response DATA was buffered (repro on the x/net β‰₯v0.60.0 floor from Friday’s security brief).

πŸ“š Worth Your Time

x/net/http2: Transport permanently leaks connection-level flow control on cancel-after-buffer

Filed 2026-10-10 (golang/go#82120). Open/unfixed. When http2.Transport.RoundTrip returns an error after response DATA was already buffered into the stream pipe (classic: short deadline + preempted caller, or cancel during cleanup), connection-level inflow taken in processData is never refunded β€” cleanupWriteRequest uses CloseWithError (leaves unread bytes) instead of BreakWithError+WINDOW_UPDATE as Body.Close does.

Concrete from the primary:

  • Repro on x/net v0.60.0 (and v0.37.0): cancel path leaks 16 KiB per errored RoundTrip; -collapse exhausts the ~1 GiB default conn window until peer RST_STREAM(FLOW_CONTROL_ERROR).
  • Production symptom (h2c client vs bRPC, ~100 ms deadlines): after ~a week, ~2 KB remote_conn_window_left, then near-total request failure on that connection without closing it.
  • Existing #49645 tie-break covers cs.abort vs respHeaderRecv, not ctx.Done/reqCancel vs respHeaderRecv.
  • Fix sketch: abandon buffered response the way transportResponseBody.Close does (BreakWithError + refund) on every nil-Response error path after stream create.
Why you care: Board Go 60. Hits anyone on long-lived HTTP/2 with aggressive timeouts β€” adjacent to Friday’s x/net β‰₯v0.60.0 bump. Awareness only (open/unfixed); promote to WC when a fix CL lands. Caveats: issue-only, no maintainer ACK yet beyond bot related-issues; not a release.
Read on golang/go#82120 β†’