coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 106 Pull requests 1 Projects Releases 737 Packages Wiki Activity Actions

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
Conversation 0 Commits 2 Files changed 3 +121 -4
coilyco-ops commented 2026-07-15 05:25:16 +00:00
Member
Copy link

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
Details
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
Details
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.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
pressure-test
Cold-read release pressure-test findings and coordination

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
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.