Fixes novox/hq issue 467: a run-once process that failed was skipped on the next apply, so ADR 0136's gate opened and the module's later resources applied what the step had refused, with no error.
Cause
A run-once process is judged done by its record (Wrote = bundle digest + unit text). It also re-runs when a restart-on resource changed in that same apply. A failure recorded nothing, so the record of the last success stayed. On the next apply nothing it reads changed again, Wrote matched, and the step returned unchanged without running.
Fix (internal/apply/apply.go, plan.go)
When a run-once process fails (the gating branch of the apply loop), its record is kept, because the unit and bundle it names are removed through it when it is undeclared, and only Wrote is cleared. The node's state is saved after a failed apply as well (cmd/mesh-host), so this persists. Every later apply then runs the step again and the gate holds. A pass records Wrote again, exactly as a first success does, and the step stops re-running.
A step that never failed behaves as today: no extra runs.
Plan says update ("its last run did not complete, so it runs again") for such a step, instead of check.
Run-once containers are unchanged. What a container reads is part of its Wrote, so a refused input already keeps it from matching its last success. A test now holds this.
Actions are unchanged (their verify asks the machine on every apply).
Tests (internal/apply/step_failed_test.go)
TestAStepThatFailedRunsAgainAndKeepsItsModuleGated: the shape found in the review of mesh-catalog #205. A file holds a value, a run-once process (restart-on that file) judges it, and a later resource in the module takes it. Apply 1 is good. Apply 2 is bad: refused, the later resource skipped. Apply 3 is unchanged: the step must run and refuse again, the later resource stays skipped and unwritten, and the apply reports the failure. The plan says update. Apply 4: the step passes and the value is written. Apply 5: not run again.
TestAStepThatNeverFailedRunsNoMoreThanBefore: four applies of one value start the step once; a changed value starts it once more.
TestAContainerStepThatFailedRunsAgain: guard; already passed on main.
On main the first test failed for the right reason: apply 3: a step that failed was not run again (started 2 times, want 3), the refused value reached the module's later resource: "bad", the plan says check.
go vet ./..., go test -race ./internal/apply/ -count=1, go test ./... and merge-check.sh pass. The bus tests were skipped: no nats-server here.
On the machines
The node-engine on ace, g14, novox and shanks. Nothing changes on a machine whose steps pass. A machine with a step failing today runs it on every apply until it passes, and reports the failure each time instead of once. mesh-catalog #205 (issue 452) waits for this rollout.
No merge without an independent review.
Fixes novox/hq issue 467: a run-once process that failed was skipped on the next apply, so ADR 0136's gate opened and the module's later resources applied what the step had refused, with no error.
## Cause
A run-once process is judged done by its record (`Wrote` = bundle digest + unit text). It also re-runs when a `restart-on` resource changed in that same apply. A failure recorded nothing, so the record of the last success stayed. On the next apply nothing it reads changed again, `Wrote` matched, and the step returned unchanged without running.
## Fix (internal/apply/apply.go, plan.go)
- When a run-once **process** fails (the gating branch of the apply loop), its record is kept, because the unit and bundle it names are removed through it when it is undeclared, and only `Wrote` is cleared. The node's state is saved after a failed apply as well (cmd/mesh-host), so this persists. Every later apply then runs the step again and the gate holds. A pass records `Wrote` again, exactly as a first success does, and the step stops re-running.
- A step that never failed behaves as today: no extra runs.
- `Plan` says `update` ("its last run did not complete, so it runs again") for such a step, instead of `check`.
- Run-once **containers** are unchanged. What a container reads is part of its `Wrote`, so a refused input already keeps it from matching its last success. A test now holds this.
- Actions are unchanged (their verify asks the machine on every apply).
## Tests (internal/apply/step_failed_test.go)
- `TestAStepThatFailedRunsAgainAndKeepsItsModuleGated`: the shape found in the review of mesh-catalog #205. A file holds a value, a run-once process (restart-on that file) judges it, and a later resource in the module takes it. Apply 1 is good. Apply 2 is bad: refused, the later resource skipped. Apply 3 is unchanged: the step must run and refuse again, the later resource stays skipped and unwritten, and the apply reports the failure. The plan says `update`. Apply 4: the step passes and the value is written. Apply 5: not run again.
- `TestAStepThatNeverFailedRunsNoMoreThanBefore`: four applies of one value start the step once; a changed value starts it once more.
- `TestAContainerStepThatFailedRunsAgain`: guard; already passed on main.
On main the first test failed for the right reason: `apply 3: a step that failed was not run again (started 2 times, want 3)`, `the refused value reached the module's later resource: "bad"`, `the plan says check`.
`go vet ./...`, `go test -race ./internal/apply/ -count=1`, `go test ./...` and `merge-check.sh` pass. The bus tests were skipped: no nats-server here.
## On the machines
The node-engine on ace, g14, novox and shanks. Nothing changes on a machine whose steps pass. A machine with a step failing today runs it on every apply until it passes, and reports the failure each time instead of once. mesh-catalog #205 (issue 452) waits for this rollout.
No merge without an independent review.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
A failure recorded nothing, so the record of the step's last success stayed and
the next apply skipped it, opening ADR 0136's gate on what it had just refused.
The record is kept, for removal, with what it was run as cleared.
Deliverynovox/mesh-host@0ec96a048eb2 — delivered since 2026-10-11T09:51:47Z
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Machines
mesh-controller on novox: passed — healthy 3 times over 4m7s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m24s
build-agent on the rest running it: sent
mesh-host on ace: passed — healthy 3 times over 3m43s
mesh-tools on every machine running it: sent
node-tools on ace: passed — judged with mesh-host: healthy 3 times over 3m43s
route-proxy on ace: passed — judged with mesh-host: healthy 3 times over 3m43s
mesh-host on the rest running it: sent
node-tools on the rest running it: sent
route-proxy on the rest running it: sent
Transitions
2026-10-11 09:12 (new) → proposed (announced): novox/mesh-host#81's head announced
2026-10-11 09:14 proposed → checked (checked): the verdict names this commit
2026-10-11 09:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 09:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 09:33 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-11 09:51 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-host@0ec96a048eb2` — **delivered** since 2026-10-11T09:51:47Z
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 4m7s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m24s
- build-agent on the rest running it: sent
- mesh-host on ace: passed — healthy 3 times over 3m43s
- mesh-tools on every machine running it: sent
- node-tools on ace: passed — judged with mesh-host: healthy 3 times over 3m43s
- route-proxy on ace: passed — judged with mesh-host: healthy 3 times over 3m43s
- mesh-host on the rest running it: sent
- node-tools on the rest running it: sent
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-11 09:12 (new) → proposed (announced): novox/mesh-host#81's head announced
- 2026-10-11 09:14 proposed → checked (checked): the verdict names this commit
- 2026-10-11 09:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 09:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 09:33 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-11 09:51 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/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
read by no module's build: internal/apply/step_failed_test.go
Run by the build seat on g14 as build-1791709671885768850 (builds --log build-1791709671885768850).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:00:50Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:00:50Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
notes:
- internal/apply/step_failed_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.017s
ok github.com/novox/mesh-host/cmd/mesh-host 5.487s
ok github.com/novox/mesh-host/examples 1.019s
ok github.com/novox/mesh-host/internal/accounts 1.453s
ok github.com/novox/mesh-host/internal/apply 2.353s
ok github.com/novox/mesh-host/internal/bootstrap 1.340s
ok github.com/novox/mesh-host/internal/bundle 1.014s
ok github.com/novox/mesh-host/internal/declaration 1.053s
ok github.com/novox/mesh-host/internal/firewall 1.663s
ok github.com/novox/mesh-host/internal/identity 1.048s
ok github.com/novox/mesh-host/internal/image 1.020s
ok github.com/novox/mesh-host/internal/inventory 1.033s
ok github.com/novox/mesh-host/internal/link 10.468s
ok github.com/novox/mesh-host/internal/liveness 2.066s
ok github.com/novox/mesh-host/internal/meshcli 1.571s
ok github.com/novox/mesh-host/internal/network 1.045s
ok github.com/novox/mesh-host/internal/outward 1.035s
ok github.com/novox/mesh-host/internal/profile 1.528s
ok github.com/novox/mesh-host/internal/reachable 1.033s
ok github.com/novox/mesh-host/internal/store 1.073s
ok github.com/novox/mesh-host/internal/system 1.011s
ok github.com/novox/mesh-host/internal/tunnel 1.015s
ok github.com/novox/mesh-host/internal/units 1.011s
ok github.com/novox/mesh-host/internal/upgrade 1.036s
ok github.com/novox/mesh-host/internal/witness 1.444s
ok github.com/novox/mesh-host/packaging 1.011s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.011s
**Merge check** at `c957f1ec`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
- read by no module's build: internal/apply/step_failed_test.go
Run by the build seat on g14 as `build-1791709671885768850` (`builds --log build-1791709671885768850`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:00:50Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:00:50Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
notes:
- internal/apply/step_failed_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.017s
ok github.com/novox/mesh-host/cmd/mesh-host 5.487s
ok github.com/novox/mesh-host/examples 1.019s
ok github.com/novox/mesh-host/internal/accounts 1.453s
ok github.com/novox/mesh-host/internal/apply 2.353s
ok github.com/novox/mesh-host/internal/bootstrap 1.340s
ok github.com/novox/mesh-host/internal/bundle 1.014s
ok github.com/novox/mesh-host/internal/declaration 1.053s
ok github.com/novox/mesh-host/internal/firewall 1.663s
ok github.com/novox/mesh-host/internal/identity 1.048s
ok github.com/novox/mesh-host/internal/image 1.020s
ok github.com/novox/mesh-host/internal/inventory 1.033s
ok github.com/novox/mesh-host/internal/link 10.468s
ok github.com/novox/mesh-host/internal/liveness 2.066s
ok github.com/novox/mesh-host/internal/meshcli 1.571s
ok github.com/novox/mesh-host/internal/network 1.045s
ok github.com/novox/mesh-host/internal/outward 1.035s
ok github.com/novox/mesh-host/internal/profile 1.528s
ok github.com/novox/mesh-host/internal/reachable 1.033s
ok github.com/novox/mesh-host/internal/store 1.073s
ok github.com/novox/mesh-host/internal/system 1.011s
ok github.com/novox/mesh-host/internal/tunnel 1.015s
ok github.com/novox/mesh-host/internal/units 1.011s
ok github.com/novox/mesh-host/internal/upgrade 1.036s
ok github.com/novox/mesh-host/internal/witness 1.444s
ok github.com/novox/mesh-host/packaging 1.011s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.011s
```
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
read by no module's build: internal/apply/step_failed_test.go
Run by the build seat on ace as build-1791709947725218410 (builds --log build-1791709947725218410).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:10:50Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:10:50Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
notes:
- internal/apply/step_failed_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.493s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.476s
ok github.com/novox/mesh-host/internal/apply 4.656s
ok github.com/novox/mesh-host/internal/bootstrap 1.518s
ok github.com/novox/mesh-host/internal/bundle 1.032s
ok github.com/novox/mesh-host/internal/declaration 1.067s
ok github.com/novox/mesh-host/internal/firewall 1.654s
ok github.com/novox/mesh-host/internal/identity 1.117s
ok github.com/novox/mesh-host/internal/image 1.038s
ok github.com/novox/mesh-host/internal/inventory 1.044s
ok github.com/novox/mesh-host/internal/link 10.478s
ok github.com/novox/mesh-host/internal/liveness 2.110s
ok github.com/novox/mesh-host/internal/meshcli 1.557s
ok github.com/novox/mesh-host/internal/network 1.053s
ok github.com/novox/mesh-host/internal/outward 1.043s
ok github.com/novox/mesh-host/internal/profile 1.506s
ok github.com/novox/mesh-host/internal/reachable 1.038s
ok github.com/novox/mesh-host/internal/store 1.223s
ok github.com/novox/mesh-host/internal/system 1.041s
ok github.com/novox/mesh-host/internal/tunnel 1.044s
ok github.com/novox/mesh-host/internal/units 1.036s
ok github.com/novox/mesh-host/internal/upgrade 1.160s
ok github.com/novox/mesh-host/internal/witness 4.642s
ok github.com/novox/mesh-host/packaging 1.046s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.040s
**Merge check** at `0ec96a04`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
- read by no module's build: internal/apply/step_failed_test.go
Run by the build seat on ace as `build-1791709947725218410` (`builds --log build-1791709947725218410`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T09:10:50Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T09:10:50Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
notes:
- internal/apply/step_failed_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.493s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.476s
ok github.com/novox/mesh-host/internal/apply 4.656s
ok github.com/novox/mesh-host/internal/bootstrap 1.518s
ok github.com/novox/mesh-host/internal/bundle 1.032s
ok github.com/novox/mesh-host/internal/declaration 1.067s
ok github.com/novox/mesh-host/internal/firewall 1.654s
ok github.com/novox/mesh-host/internal/identity 1.117s
ok github.com/novox/mesh-host/internal/image 1.038s
ok github.com/novox/mesh-host/internal/inventory 1.044s
ok github.com/novox/mesh-host/internal/link 10.478s
ok github.com/novox/mesh-host/internal/liveness 2.110s
ok github.com/novox/mesh-host/internal/meshcli 1.557s
ok github.com/novox/mesh-host/internal/network 1.053s
ok github.com/novox/mesh-host/internal/outward 1.043s
ok github.com/novox/mesh-host/internal/profile 1.506s
ok github.com/novox/mesh-host/internal/reachable 1.038s
ok github.com/novox/mesh-host/internal/store 1.223s
ok github.com/novox/mesh-host/internal/system 1.041s
ok github.com/novox/mesh-host/internal/tunnel 1.044s
ok github.com/novox/mesh-host/internal/units 1.036s
ok github.com/novox/mesh-host/internal/upgrade 1.160s
ok github.com/novox/mesh-host/internal/witness 4.642s
ok github.com/novox/mesh-host/packaging 1.046s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.040s
```
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.
Fixes novox/hq issue 467: a run-once process that failed was skipped on the next apply, so ADR 0136's gate opened and the module's later resources applied what the step had refused, with no error.
Cause
A run-once process is judged done by its record (
Wrote= bundle digest + unit text). It also re-runs when arestart-onresource changed in that same apply. A failure recorded nothing, so the record of the last success stayed. On the next apply nothing it reads changed again,Wrotematched, and the step returned unchanged without running.Fix (internal/apply/apply.go, plan.go)
Wroteis cleared. The node's state is saved after a failed apply as well (cmd/mesh-host), so this persists. Every later apply then runs the step again and the gate holds. A pass recordsWroteagain, exactly as a first success does, and the step stops re-running.Plansaysupdate("its last run did not complete, so it runs again") for such a step, instead ofcheck.Wrote, so a refused input already keeps it from matching its last success. A test now holds this.Tests (internal/apply/step_failed_test.go)
TestAStepThatFailedRunsAgainAndKeepsItsModuleGated: the shape found in the review of mesh-catalog #205. A file holds a value, a run-once process (restart-on that file) judges it, and a later resource in the module takes it. Apply 1 is good. Apply 2 is bad: refused, the later resource skipped. Apply 3 is unchanged: the step must run and refuse again, the later resource stays skipped and unwritten, and the apply reports the failure. The plan saysupdate. Apply 4: the step passes and the value is written. Apply 5: not run again.TestAStepThatNeverFailedRunsNoMoreThanBefore: four applies of one value start the step once; a changed value starts it once more.TestAContainerStepThatFailedRunsAgain: guard; already passed on main.On main the first test failed for the right reason:
apply 3: a step that failed was not run again (started 2 times, want 3),the refused value reached the module's later resource: "bad",the plan says check.go vet ./...,go test -race ./internal/apply/ -count=1,go test ./...andmerge-check.shpass. The bus tests were skipped: no nats-server here.On the machines
The node-engine on ace, g14, novox and shanks. Nothing changes on a machine whose steps pass. A machine with a step failing today runs it on every apply until it passes, and reports the failure each time instead of once. mesh-catalog #205 (issue 452) waits for this rollout.
No merge without an independent review.
Delivery
novox/mesh-host@0ec96a048eb2— delivered since 2026-10-11T09:51:47ZDelivery plan — builds mesh-host → 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
c957f1ecmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791709671885768850(builds --log build-1791709671885768850).Merge check at
0ec96a04mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791709947725218410(builds --log build-1791709947725218410).