Go: Idle Connections Get an Audit

Today's activity centers on network stack reliability — a pair of net/http fixes closes a deadlock and two memory regressions tied to recent idle-connection optimizations, while a separate cleanup fixes a linker probe that silently broke builds using compiler wrapper scripts.

Duration: PT2M49S

Episode overview

This episode is a short developer briefing from Go.

It explains recent repository work in plain language.

  • Show: Go
  • Published: 2026-09-10T13:08:08Z
  • Audio duration: PT2M49S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good day, and welcome to Go, your daily developer briefing for September 10th, 2026.

The clearest signal today: recent work to slim down idle HTTP connections introduced real regressions, and the team is now cleaning those up fast.

Start with commit b35e1f9 from Brad Fitzpatrick. A prior change meant to stop pinning buffer memory on idle keep-alive connections broke connections over non-standard net-dot-Conn implementations — think Tailscale's network stack — because its idle timeout probe checked for a specific error type that those…

Alongside that, commit e51216d from Nicholas Husin fixes a genuine deadlock: closing an HTTP/1 response body early while a read is in flight could leave both operations waiting on the same signal, one that only fires once. That's now resolved by separating early-close from normal completion signaling.

The throughline here is that performance and memory optimizations to the HTTP stack are getting real-world stress testing, and the fixes are landing quickly — a good reminder that idle-connection behavior deserves extra scrutiny before it ships.

Separately, PR 81410 from KingLizard1020 fixes cmd/link: when the C compiler is invoked through a wrapper with…

Nearby episodes from Go

  1. A Revert, a Regression Fix, and Type-System Guardrails
  2. Compiler Rewrite Packages Get Reorganized
  3. Formatting Precision Fix
  4. Weekly Recap - Security Hardening and Runtime Memory Discipline
  5. Fixing Vet's Failure Handling in Multi-Package Tests
  6. Certificate Parsing Gets Stricter, TLS Memory Gets Leaner
  7. Plugin Bug Fix and Protocol Correctness
  8. SVE Expands, Compiler Correctness Cleanup