Daily Engineering Intelligence

Technology Newspaper

← Back to Home

Engineering Intelligence β€” Saturday

October 10, 2026

πŸ”₯ What Changed

Quiet Saturday. Cloudflare shipped on-demand CPU and heap profiling for Workers and Durable Objects β€” production flamegraphs without spinning a fresh isolate or stopping traffic. Two longer reads: VictoriaMetrics on a documented net/http Client.Do body race (same root cause, opposite product decisions in vmagent vs vmauth), and Harvey’s MCP Policy Engine (complete mediation and fail-closed authorization after connect).

Go stays quiet after yesterday’s 1.27.2 / 1.26.9 security release. #82026 still has CL 846325 NEW with no merge β€” held. #81957 has Pratt CL 847406 under review β€” held. #81759 is open; #81864 remains tip-only. Azure PIR finals 7Q30-010 / 7QL5-Z50 are still preliminary (expect ~10-13/14). grpc-go v1.85 is due ~10-13.

Cloudflare: on-demand CPU/heap profiling for Workers & Durable Objects

Published 2026-10-09. Production on-demand CPU and memory profiles with interactive flamegraphs β€” from the dashboard (Observability β†’ Flamegraph) or cf workers versions profile. You must pick a version that already has enough traffic; Cloudflare does not spin a new isolate just for profiling.

Design details (from the primary):

  • Isolate lock is held only for profiler start and stop; during capture the lock is released so requests continue.
  • Samples are 1 ms V8 CPU samples; memory profiles cover the live heap.
  • Durable Object profiling routes by name to the live primary actor (not a random replica).
  • Real fixes from the profiles: a recursive JSON.stringify replacer that walked the tree while stringify already walked it β†’ 2.7Γ— faster after the fix; a β€œdisabled” Prometheus path that still allocated β†’ P999 heap 133 β†’ 118 MB under a 128 MB limit (path removed).
  • Continuous profiling is on the roadmap.
Why you care: Board DistSys 48; Observability. Transferable lesson for any replicated stateful runtime: how to attach a profiler to the live primary without stopping traffic, and how short critical sections (start/stop only) keep the request path free. Caveats: Workers / JS / V8, not Go β€” treat the isolate/primary routing and lock discipline as the portable part.
Read on Cloudflare Blog β†’

πŸ“š Worth Your Time

VictoriaMetrics: The Data Race That Wasn't a Bug (and the One That Was)

Published 2026-10-06; surfaced in Golang Weekly #620 (Oct 9) with valyala linking golang/go#81445 the same day. Client.Do / Post can return while persistConn.writeLoop is still reading req.Body β€” the documented RoundTripper / Client.Do async Close behavior.

Same root cause, opposite decisions:

  • vmagent kept a race-detector-flagged shared []byte behind fresh readers: mixed bytes go nowhere after an early 502/200 + Connection: close, so they accepted the race as harmless in practice.
  • vmauth fixed a shared stateful reader/offset that could silently corrupt retry bodies sent to healthy backends β€” that one was a real bug.

Ties to open #81445 (Damien Neil floated Request.Close as a possible API). Practical rules: assume the transport may still read the body after Do returns; don’t share a stateful Reader across requests; be careful mutating pooled body memory until Close.

Why you care: Board Go 60. Every Go HTTP client that retries with a body, pools buffers, or wraps io.Reader hits this. The dual outcome (keep vs fix) is the teaching point β€” race-detector hits are not automatically bugs, but shared mutable offset state across retries is. Caveats: post dated 10-06; Weekly #620 / #81445 are the Saturday surfacing.
Read on VictoriaMetrics Blog β†’  Β·  golang/go#81445 β†’

Harvey: Building Harvey's MCP Policy Engine

Published 2026-10-07. Harvey describes a runtime MCP Policy Engine with complete mediation: every tools/call is checked; connecting successfully does not authorize every later action.

Design (from the primary):

  • Tool Pinner records approved tool descriptions and schemas; discovery diffs go to Security review before use.
  • Trajectory eval with Rego / Regorus on tool IDs + Harvey annotations + call history (not prompt or customer data) β†’ permit / deny / pause.
  • Fail closed if checks can’t complete; workspace settings cannot override an engine denial.
  • Argument capacity Γ— authority analysis; sanitizer for hidden / lookalike characters; cycle detection for agent-to-agent tool chains.

Complements 10-06 MCP OAuth issuer binding and the 10-08 Cloudflare SecOps / Temporal Pi thread on a third axis: authorization after connect.

Why you care: Auth/IAM rising on the board; AI agents (Tier-2). Reference-monitor pattern for MCP β€” pin schemas, mediate every call, fail closed, keep policy inputs off the prompt. Caveats: vendor legal-AI showcase; no quantitative red-team numbers; Regorus is not Go-native; fine-grained pinning called β€œdeveloping”; prompt injection remains an open problem.
Read on Harvey Blog β†’