Issue 1772: the check's throwaway store (postgres, which declares VOLUME) and bus were removed with docker rm -f without -v at the end of a check, on failure or timeout, on a kill, on an earlier delivery of the same ask and at the holder's start, so each check left anonymous volumes behind (1,629 volumes, 107 GB on one build node by 2026-10-21). removeWithVolumes reads the volumes the labelled containers mount, removes the containers with rm -f -v, then removes any of those anonymous volumes still there; a named volume, a bind mount or a volume another container uses is never removed. same_program.go and the Makefile's postgres targets take -v too. The disk condition that should have warned is issue 1789.
Issue 1772: the check's throwaway store (postgres, which declares VOLUME) and bus were removed with `docker rm -f` without -v at the end of a check, on failure or timeout, on a kill, on an earlier delivery of the same ask and at the holder's start, so each check left anonymous volumes behind (1,629 volumes, 107 GB on one build node by 2026-10-21). removeWithVolumes reads the volumes the labelled containers mount, removes the containers with `rm -f -v`, then removes any of those anonymous volumes still there; a named volume, a bind mount or a volume another container uses is never removed. same_program.go and the Makefile's postgres targets take -v too. The disk condition that should have warned is issue 1789.
Reviewed-by: reviewer-1772@shanks at d491356f59dd460850311fbb04a4c3604d179f47
mesh/merge-gate head d491356f59dd merged into trunk 1f3fdf311167 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
Deliverynovox/mesh-controller@d491356f59dd — delivered since 2026-10-21T21:24:05Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
Machines
mesh-controller on every machine running it: sent
build-agent on every machine running it: sent
Transitions
2026-10-21 20:53 (new) → proposed (announced): novox/mesh-controller#431's head announced
2026-10-21 21:07 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-21 21:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-21 21:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-21 21:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-21 21:24 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@d491356f59dd` — **delivered** since 2026-10-21T21:24:05Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
**Machines**
- mesh-controller on every machine running it: sent
- build-agent on every machine running it: sent
**Transitions**
- 2026-10-21 20:53 (new) → proposed (announced): novox/mesh-controller#431's head announced
- 2026-10-21 21:07 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-21 21:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-21 21:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-21 21:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-21 21:24 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Merge check at d491356f
Judged: head d491356f59dd merged into trunk 1f3fdf311167; read beside it: mesh-catalog 379317589488, mesh-controller-main 1f3fdf311167, mesh-host 4065b45ae84f, mesh-tools e0fadc43d9dd
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
read by no module's build: Makefile, cmd/mesh-builder/holder_test.go, internal/builder/kill_test.go
Run by the build seat on ace as build-1792616008052909640 (builds --log build-1792616008052909640).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue 1772: the check's throwaway store (postgres, which declares VOLUME) and bus were removed with
docker rm -fwithout -v at the end of a check, on failure or timeout, on a kill, on an earlier delivery of the same ask and at the holder's start, so each check left anonymous volumes behind (1,629 volumes, 107 GB on one build node by 2026-10-21). removeWithVolumes reads the volumes the labelled containers mount, removes the containers withrm -f -v, then removes any of those anonymous volumes still there; a named volume, a bind mount or a volume another container uses is never removed. same_program.go and the Makefile's postgres targets take -v too. The disk condition that should have warned is issue 1789.Reviewed-by: reviewer-1772@shanks at
d491356f59Delivery
novox/mesh-controller@d491356f59dd— delivered since 2026-10-21T21:24:05ZDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
d491356fJudged: head
d491356f59ddmerged into trunk1f3fdf311167; read beside it: mesh-catalog379317589488, mesh-controller-main1f3fdf311167, mesh-host4065b45ae84f, mesh-toolse0fadc43d9ddmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1792616008052909640(builds --log build-1792616008052909640).