Replay the silent web application: its declared HTTP check raises it within two looks (hq ADR 0240 Phase B, issue 145) #55

2026-10-07T12:52:31Z

mesh-admin commented

2026-10-07 12:52:31 +00:00

R145 in the register, kind Liveness (two repositories move together, like R-crashloop): a busybox httpd whose CGI application never answers is raised here; the node-engine at its commit looks at it with the module's declared HTTP check (2 looks, 10 s); the controller at its commit raises module.app.anchor.unhealthy on the second statement.

go run ./cmd/prove R145: PROVED — before its fix fails, on its fix passes (before: the engine at main does not look at a declared HTTP check).

The Fix refs name feat/health-the-field in mesh-controller and mesh-host; repoint them at the merge commits once those merge (as R-crashloop's were).

check-here: repo-check PASS.

R145 in the register, kind Liveness (two repositories move together, like R-crashloop): a busybox httpd whose CGI application never answers is raised here; the node-engine at its commit looks at it with the module's declared HTTP check (2 looks, 10 s); the controller at its commit raises `module.app.anchor.unhealthy` on the second statement. `go run ./cmd/prove R145`: **PROVED — before its fix fails, on its fix passes** (before: the engine at main does not look at a declared HTTP check). The `Fix` refs name `feat/health-the-field` in mesh-controller and mesh-host; repoint them at the merge commits once those merge (as R-crashloop's were). check-here: repo-check PASS.

mesh-admin added 1 commit 2026-10-07 12:52:31 +00:00

Replay the silent web application: its declared HTTP check raises it within two looks (hq ADR 0240 Phase B, issue 145)

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

mesh/delivery-group group feat/health-the-field delivered: every member is delivered

Details

d93f1e4eab

For eleven hours a web application's port was open and its program ran while
every request hung; liveness and a TCP check both say it fine. R145 raises a
web server whose application never answers, has the node-engine at its commit
look at it with the module's declared HTTP check, and the controller at its
commit raise the module's condition on the second look. Proved: it fails on
the trunk before Phase B and passes on it.

mesh-admin commented

2026-10-07 13:13:30 +00:00

Delivery novox/mesh-lab@d93f1e4eab73 — delivered since 2026-10-07T16:28:53Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Group feat/health-the-field, in order: novox/mesh-lab@d93f1e4eab

novox/mesh-controller@b98fd0f396 before novox/mesh-host@96bf9415aa: built by
novox/mesh-host@96bf9415aa before novox/mesh-controller@b98fd0f396: engine before controller

Transitions

2026-10-07 13:12 (new) → proposed (announced): novox/mesh-lab#55's head announced
2026-10-07 13:13 proposed → checked (checked): the verdict names this commit
2026-10-07 13:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 16:28 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-07 16:28 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-lab@d93f1e4eab73` — **delivered** since 2026-10-07T16:28:53Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Group** `feat/health-the-field`, in order: novox/mesh-lab@d93f1e4eab73 - novox/mesh-controller@b98fd0f396c8 before novox/mesh-host@96bf9415aae4: built by - novox/mesh-host@96bf9415aae4 before novox/mesh-controller@b98fd0f396c8: engine before controller **Transitions** - 2026-10-07 13:12 (new) → proposed (announced): novox/mesh-lab#55's head announced - 2026-10-07 13:13 proposed → checked (checked): the verdict names this commit - 2026-10-07 13:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 16:28 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 16:28 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin merged commit 3d871c992d into main

2026-10-07 16:28:35 +00:00

mesh-admin deleted branch feat/health-the-field

2026-10-07 16:28:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#55