Issue 1277 (met three times: design 47 R3c, R3e and R4c-3's delivery plan-1792532598997838436): a delivery that rebuilds gitea asked the forge's address during its re-serve; newSourceForms cached the failed read as an empty base, onTheForge then answered every source off the forge, and the registration refused 'not on the mesh's forge'. Now: a failed read is never cached as known (kept 5 s, so a catalogue loop composes once); a registration reads the address again within the one 60 s bound it shares with the forge's protection question (issue 486's bound, so the receive loop is never held longer); 'not on the mesh's forge' is said only with the address known; an unreadable address is refused naming its error. Terminal registration is unchanged (ADR 0266). 1277/AC1-AC4 unit tests; AC5 live: the Retry of plan-1792532598997838436 after this is delivered.
Try build-1792533911804837518 passed at this head (6m26s, unit level 2.44 s of 5 s).
Issue 1277 (met three times: design 47 R3c, R3e and R4c-3's delivery plan-1792532598997838436): a delivery that rebuilds gitea asked the forge's address during its re-serve; newSourceForms cached the failed read as an empty base, onTheForge then answered every source off the forge, and the registration refused 'not on the mesh's forge'. Now: a failed read is never cached as known (kept 5 s, so a catalogue loop composes once); a registration reads the address again within the one 60 s bound it shares with the forge's protection question (issue 486's bound, so the receive loop is never held longer); 'not on the mesh's forge' is said only with the address known; an unreadable address is refused naming its error. Terminal registration is unchanged (ADR 0266). 1277/AC1-AC4 unit tests; AC5 live: the Retry of plan-1792532598997838436 after this is delivered.
Try build-1792533911804837518 passed at this head (6m26s, unit level 2.44 s of 5 s).
Reviewed-by: review-fix-1277@shanks at 2b1eeb7cd53edc106854c74a0ef87a3578196b38
mesh/merge-gate head 2b1eeb7cd53e merged into trunk f29d193ddbc1 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang…
Deliverynovox/mesh-controller@2b1eeb7cd53e — delivered since 2026-10-20T22:37:34Z
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
Machines
mesh-controller on every machine running it: sent
Transitions
2026-10-20 22:14 (new) → proposed (announced): novox/mesh-controller#411's head announced
2026-10-20 22:32 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-20 22:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-20 22:34 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-20 22:34 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-20 22:37 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@2b1eeb7cd53e` — **delivered** since 2026-10-20T22:37:34Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Machines**
- mesh-controller on every machine running it: sent
**Transitions**
- 2026-10-20 22:14 (new) → proposed (announced): novox/mesh-controller#411's head announced
- 2026-10-20 22:32 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-20 22:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-20 22:34 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-20 22:34 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-20 22:37 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`.
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 1277 (met three times: design 47 R3c, R3e and R4c-3's delivery plan-1792532598997838436): a delivery that rebuilds gitea asked the forge's address during its re-serve; newSourceForms cached the failed read as an empty base, onTheForge then answered every source off the forge, and the registration refused 'not on the mesh's forge'. Now: a failed read is never cached as known (kept 5 s, so a catalogue loop composes once); a registration reads the address again within the one 60 s bound it shares with the forge's protection question (issue 486's bound, so the receive loop is never held longer); 'not on the mesh's forge' is said only with the address known; an unreadable address is refused naming its error. Terminal registration is unchanged (ADR 0266). 1277/AC1-AC4 unit tests; AC5 live: the Retry of plan-1792532598997838436 after this is delivered.
Try build-1792533911804837518 passed at this head (6m26s, unit level 2.44 s of 5 s).
Reviewed-by: review-fix-1277@shanks at
2b1eeb7cd5Delivery
novox/mesh-controller@2b1eeb7cd53e— delivered since 2026-10-20T22:37:34ZDelivery plan — builds mesh-controller → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
2b1eeb7cJudged: head
2b1eeb7cd53emerged into trunkf29d193ddbc1; read beside it: mesh-catalog199f72fed29d, mesh-controller-mainf29d193ddbc1, mesh-hostce1b97ad973d, mesh-tools18260ce9becamesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on shanks as
build-1792534481009959473(builds --log build-1792534481009959473).