Repository navigation
Error message: tell a refused connection from a stream that sent no event #511
Description
On a refused port, the subscription fails with "The opencode event stream did not connect within 2 seconds", which reads like a slow server.
Proposed: distinguish "connection refused" from "connected, but no event arrived" in the message.
Source: internal developer-experience evaluation of the 2.0.32 nightly, 2026-10-18 (finding D32-13).
Activity
Pipelineis split, and the reconnect loop gets an owning type #483Blind-Striker commentedon Oct 23, 2026
Moved from the documentation sweep (#504) to RT-E4 (#483): the fix is a change to the message in hand-written transport (
src/OpenCode.Sdk/Internal/Transport/Pipeline.csandStreamAttempt.cs, where "did not connect within" is raised), not a documentation edit.docs: changelog for #511; the attempt's response flag says what order…