novox/hq
6
0
Fork 0
Code Issues Pull Requests 6 Releases Wiki Activity

Issue 351: a held delivery whose module a backlog walk carried to every machine is never covered #251

Merged
mesh-admin merged 1 commits from issues/351-a-held-delivery-whose-module-a-backlog-walk-carried-is-never-covered into main 2026-10-09 15:01:44 +00:00
Conversation 1 Commits 1 Files Changed 3
+148
mesh-admin commented 2026-10-09 14:54:08 +00:00
Contributor
Copy Link
Copy Source

The catalogue's #125 (openrazer, issue 316) stayed held 28 hours after ADR 0270 went live, raising delivery.<id>.stalled every hour, while the module built from #127's merge ran on both of its machines. ADR 0270 covers a held merge when a later delivered walk sent its module everywhere, as the machine steps say; a build the mesh held back for a person and sent on the operator's word travels by a backlog walk, which gives one step per machine, and whose end mesh-delivery read for nothing.

  • 04-ISSUES/351: the report (symptom, the day's timeline, what was ruled out) and the diagnosis, located in mesh-delivery (creditBacklog, carries), with the fix as built and how it is checked.
  • ADR 0270: a progressive insight on the consequence that named the one-machine gap, which this widens; the decision stands.

The fix is mesh-catalog #163 (three tests that fail on main before it). The four checks pass.

The catalogue's #125 (openrazer, issue 316) stayed `held` 28 hours after ADR 0270 went live, raising `delivery.<id>.stalled` every hour, while the module built from #127's merge ran on both of its machines. ADR 0270 covers a held merge when a later delivered walk sent its module everywhere, as the machine steps say; a build the mesh held back for a person and sent on the operator's word travels by a backlog walk, which gives one step per machine, and whose end mesh-delivery read for nothing. - `04-ISSUES/351`: the report (symptom, the day's timeline, what was ruled out) and the diagnosis, located in mesh-delivery (`creditBacklog`, `carries`), with the fix as built and how it is checked. - ADR 0270: a progressive insight on the consequence that named the one-machine gap, which this widens; the decision stands. The fix is mesh-catalog #163 (three tests that fail on main before it). The four checks pass.
mesh-admin added 1 commit 2026-10-09 14:54:08 +00:00
Issue 351: a held delivery whose module a backlog walk carried to every machine is never covered
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
261bee1cab 
The catalogue's #125 stayed held 28 hours after ADR 0270 went live. The record covers a held merge when a
later delivered walk sent its module everywhere, as the machine steps say; a build held back for a person
and sent on the operator's word travels by a backlog walk, which gives one step per machine and whose end
mesh-delivery read for nothing. Report, diagnosis located in mesh-delivery, the fix in mesh-catalog #163,
and a progressive insight on ADR 0270's one-machine consequence, which this widens.
mesh-admin commented 2026-10-09 14:54:22 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/hq@261bee1cab04 — delivered since 2026-10-09T15:02:15Z

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

Transitions

  • 2026-10-09 14:54 (new) → proposed (announced): novox/hq#251's head announced
  • 2026-10-09 14:54 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 14:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 15:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-09 15:02 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-delivery:view --> **Delivery** `novox/hq@261bee1cab04` — **delivered** since 2026-10-09T15:02:15Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-09 14:54 (new) → proposed (announced): novox/hq#251's head announced - 2026-10-09 14:54 proposed → checked (checked): the verdict names this commit - 2026-10-09 14:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 15:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 15:02 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 793e98d45a into main 2026-10-09 15:01:44 +00:00
mesh-admin deleted branch issues/351-a-held-delivery-whose-module-a-backlog-walk-carried-is-never-covered 2026-10-09 15:01:45 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
jschoubben miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#251