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

coilyco-ops commented

2026-07-15 03:43:22 +00:00

Owner

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

coilyco-ops added 1 commit

2026-07-15 03:43:22 +00:00

Fix broker launch conflict cleanup

test / test (pull_request) Successful in 48s

Details

988d2b0cab