From 9d78c28c21b69d059c207bac7420e5a4a31e46b3 Mon Sep 17 00:00:00 2001 From: hamr0 Date: Sun, 26 Jul 2026 02:22:08 +0200 Subject: [PATCH] docs: correct BA-18 idle-gap figure in CHANGELOG (measured, not the filed estimate) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 0.34.0 entry cited "idled the connection 40–56s between turns" — a figure from the filed ask that the adopter's later F57 archive analysis disproved. Real measured idle gaps: median ~4s, max ~49s on the affected job; another job idled up to 561s. The hang durations (38 min ×2, 2h24m ×1, 3/3) were correct and are unchanged. Docs-only; the published 0.34.0 tarball keeps the old number (npm is immutable) — this corrects main for the record and the next release. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01EWGqnWr4Qn3gDnHrE3DaZi --- CHANGELOG.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5034b6f..26b5e39 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,9 +11,10 @@ All notable changes to bare-agent are documented here. Format: [Keep a Changelog wired — no socket timeout, no `AbortSignal` — so a socket the server silently dropped, or a response that never starts, was bounded only by the **OS TCP timeout (~2h on Linux)**. It presented to the caller as a *hang*, not a failure (no event, no error, no progress), which made - every retry/casualty policy above it inert by construction. Observed by an adopter 3/3 times a job - idled the connection 40–56s between turns: a single `generate()` never returned for **38 min** - (twice) and **2h24m** (once). + every retry/casualty policy above it inert by construction. Observed by an adopter 3/3 times, on a + job that idles the connection between turns (measured idle gaps: median ~4s, max ~49s on that job; + up to 561s on another): a single `generate()` never returned for **38 min** (twice) and **2h24m** + (once). - New `timeoutMs` option on all four providers (constructor default **600000ms / 10 min**; overridable per call via `generate(..., { timeoutMs })`). It bounds on socket **inactivity** (`req.setTimeout`), so a slow-but-streaming response is not killed — only a silent or