Keep the host dispatch broker alive after brokered dispatch failures #1322

Merged
coilyco-ops merged 2 commits from issue-1243 into main 2026-07-15 05:41:13 +00:00
Owner

This narrows the dispatch broker boundary so a failed launch stays local to that request. It recovers panics at the request/launch boundary, serializes the failure back to the caller, and keeps the listener accepting later requests. I also added regression coverage for a Docker name-conflict-shaped failure followed by a later brokered request.

  • Keeps the host broker alive after per-request failures
  • Classifies Docker 125/name-conflict-shaped failures as request failures
  • Covers the retry path with a listener-level regression

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

This narrows the dispatch broker boundary so a failed launch stays local to that request. It recovers panics at the request/launch boundary, serializes the failure back to the caller, and keeps the listener accepting later requests. I also added regression coverage for a Docker name-conflict-shaped failure followed by a later brokered request. - Keeps the host broker alive after per-request failures - Classifies Docker 125/name-conflict-shaped failures as request failures - Covers the retry path with a listener-level regression closes #1243 ward.workflow: pull-request-and-merge
Harden host dispatch broker request boundary
Some checks failed
test / test (pull_request) Failing after 48s
67f1678eef
Keep the host dispatch broker serving after per-request failures, including Docker 125/name-conflict-shaped panics, and add regression coverage for a later request reaching the broker.
Harden host dispatch broker request boundary
All checks were successful
test / test (pull_request) Successful in 4m8s
17c4008cf3
Keep the host dispatch broker serving after per-request failures, including Docker 125/name-conflict-shaped panics, and add regression coverage for a later request reaching the broker.
Commenting is not possible because the repository is archived.
No reviewers
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward!1322
No description provided.