Issue 281: a tier sent one module at a time blamed a module for its machine #154

Merged
mesh-admin merged 1 commits from issues/281-a-tier-sent-one-module-at-a-time-blamed-a-module-for-its-machine into main 2026-10-06 20:26:05 +00:00
Contributor

Opens issue 281, status located, fixed by novox/mesh-controller PR #100.

A plan sent a wide tier to its first machine one module at a time, a whole declaration per module. The churn raised core-behind on the machine, and the gate failed the module it was judging for that machine-level condition. The rollback then read "what the machine ran before" after an earlier send of the same tier had already carried the new build there, so it searched for a predecessor of the very commit it failed. The fix sends a tier to each machine once, judges it with one gate, sorts machine-level conditions (named module / core settling / machine as a whole), and treats a send that changed nothing of a module as no verdict on its build.

Role names only. records.py, index.py and cycle.py pass. The core-issue replay: is still to come before resolution.

Opens issue 281, status `located`, fixed by novox/mesh-controller PR #100. A plan sent a wide tier to its first machine one module at a time, a whole declaration per module. The churn raised `core-behind` on the machine, and the gate failed the module it was judging for that machine-level condition. The rollback then read "what the machine ran before" after an earlier send of the same tier had already carried the new build there, so it searched for a predecessor of the very commit it failed. The fix sends a tier to each machine once, judges it with one gate, sorts machine-level conditions (named module / core settling / machine as a whole), and treats a send that changed nothing of a module as no verdict on its build. Role names only. `records.py`, `index.py` and `cycle.py` pass. The core-issue `replay:` is still to come before resolution.
mesh-admin added 1 commit 2026-10-06 20:25:30 +00:00
Issue 281: a tier sent one module at a time blamed a module for its machine
mesh/merge-gate the mesh is checking this head against every machine
mesh/delivery delivered
0555508020
mesh-admin merged commit 9bd54ee05d into main 2026-10-06 20:26:05 +00:00
mesh-admin deleted branch issues/281-a-tier-sent-one-module-at-a-time-blamed-a-module-for-its-machine 2026-10-06 20:26:05 +00:00
Author
Contributor

Delivery novox/hq@055550802096 — delivered since 2026-10-09T07:31:48Z

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

Transitions

  • 2026-10-06 23:05 (new) → proposed (announced): novox/hq#154's head announced
  • 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
  • 2026-10-09 07:31 held → delivered (done): merged, and nothing for a walk to move: builds nothing: the change touches no module of the mesh's graph

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

<!-- mesh-delivery:view --> **Delivery** `novox/hq@055550802096` — **delivered** since 2026-10-09T07:31:48Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#154's head announced - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-09 07:31 held → delivered (done): merged, and nothing for a walk to move: builds nothing: the change touches no module of the mesh's graph The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#154