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

Fix broker cleanup on Docker name conflicts #1306

Merged
coilyco-ops merged 1 commit from issue-1282 into main 2026-07-15 03:44:51 +00:00
Conversation 0 Commits 1 Files changed 2 +58 -1
coilyco-ops commented 2026-07-15 03:43:22 +00:00
Member
Copy link

This change keeps the broker from treating a Docker duplicate-name refusal as a reason to stop the live engineer container. When a launch collides with an existing container name, the broker now records the failure, unlocks the issue, and leaves the existing run alone instead of trying to clean it up by name.

  • Added a duplicate-name detector in the broker failure path.
  • Added a regression test that proves the stop call is skipped for the conflict case.
  • Validation: ward exec test and pre-commit run --all-files.

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

This change keeps the broker from treating a Docker duplicate-name refusal as a reason to stop the live engineer container. When a launch collides with an existing container name, the broker now records the failure, unlocks the issue, and leaves the existing run alone instead of trying to clean it up by name. - Added a duplicate-name detector in the broker failure path. - Added a regression test that proves the stop call is skipped for the conflict case. - Validation: `ward exec test` and `pre-commit run --all-files`. closes #1282 ward.workflow: pull-request-and-merge
Fix broker launch conflict cleanup
All checks were successful
test / test (pull_request) Successful in 48s
Details
988d2b0cab 
closes #1282
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!1306
No description provided.