Fix dispatch broker EOF response handling #1291

Merged

coilysiren merged 1 commit from issue-1281 into main

2026-07-14 21:05:45 +00:00

coilyco-ops commented

2026-07-14 19:06:18 +00:00

Member

Keeps a single failed launch from surfacing as a raw transport EOF.
Adds a regression for a dropped response followed by a successful request.
Tests: go test ./cmd/ward -run 'TestSendDispatchBrokerLaunchRequest(WaitsForResponse|ReportsDroppedResponse)$' -count=1
Full ward exec test was blocked here by temporary cache-space limits in the container.

closes #1281
ward.workflow: pull-request-and-merge

This change keeps brokered sibling dispatch alive when the host side closes the response stream before replying. EOF now returns a structured launch error, and a regression proves the broker still answers a later request after one dropped response. - Keeps a single failed launch from surfacing as a raw transport EOF. - Adds a regression for a dropped response followed by a successful request. - Tests: `go test ./cmd/ward -run 'TestSendDispatchBrokerLaunchRequest(WaitsForResponse|ReportsDroppedResponse)$' -count=1` - Full `ward exec test` was blocked here by temporary cache-space limits in the container. closes #1281 ward.workflow: pull-request-and-merge

coilyco-ops added 1 commit

2026-07-14 19:06:18 +00:00