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

Playbook 08: a fix that moves a file to a new filler compares the values first (issue 957) #391

Merged
mesh-tools merged 1 commits from fix/957-playbook-08-first-fill into main 2026-10-16 21:56:25 +00:00
Conversation 5 Commits 1 Files Changed 1
+9
mesh-tools commented 2026-10-16 20:58:35 +00:00
Member
Copy Link
Copy Source

The lesson of issue 957, under playbook 08's "when a playbook meets a problem". On 2026-10-16 the forge and the identity provider on the control node were down for 17 minutes, because postgres's consumers were served the port inside its container instead of the published port, the first time the provisioner client filled their files.

The new paragraph, before Bounds: a fix that makes a module's file filled a new way for the first time lists every value the old way put there on each machine, and shows in its review that the new way gives the same values (or which differ and why). The values are read from the machines before the merge, not from the code.

A few lines of playbook text: the operator's word on this pull request is its review (playbook 08 step 4). hq's merge-check.sh passed locally. It merges cleanly beside hq #384, which edits other lines of the same file.

The lesson of issue 957, under playbook 08's "when a playbook meets a problem". On 2026-10-16 the forge and the identity provider on the control node were down for 17 minutes, because postgres's consumers were served the port inside its container instead of the published port, the first time the provisioner client filled their files. The new paragraph, before Bounds: a fix that makes a module's file filled a new way for the first time lists every value the old way put there on each machine, and shows in its review that the new way gives the same values (or which differ and why). The values are read from the machines before the merge, not from the code. A few lines of playbook text: the operator's word on this pull request is its review (playbook 08 step 4). hq's merge-check.sh passed locally. It merges cleanly beside hq #384, which edits other lines of the same file.
mesh-tools added 1 commit 2026-10-16 20:58:35 +00:00
Playbook 08: a fix that moves a file to a new filler compares the values first (issue 957)
mesh/merge-gate head 78353ad272a3 merged into trunk f795356ae1d6 — pass: the change touches no module of the mesh's graph
Details
mesh/repo-check head 78353ad272a3 merged into trunk f795356ae1d6 — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
78353ad272
mesh-tools commented 2026-10-16 20:58:47 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/hq@78353ad272a3 — delivered since 2026-10-16T21:56:27Z

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

Transitions

  • 2026-10-16 20:58 (new) → proposed (announced): novox/hq#391's head announced
  • 2026-10-16 20:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 20:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 21:50 ready → proposed (trunk moved): out of date: judged against trunk f9c240a957, the trunk is now f795356ae1d6; judged again on a recheck or when it is merged
  • 2026-10-16 21:56 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 21:56 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 21:56 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-16 21:56 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@78353ad272a3` — **delivered** since 2026-10-16T21:56:27Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-16 20:58 (new) → proposed (announced): novox/hq#391's head announced - 2026-10-16 20:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 20:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 21:50 ready → proposed (trunk moved): out of date: judged against trunk f9c240a957b8, the trunk is now f795356ae1d6; judged again on a recheck or when it is merged - 2026-10-16 21:56 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 21:56 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 21:56 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 21:56 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`.
jschoubben added the mesh/ready label 2026-10-16 21:38:11 +00:00
mesh-tools removed the mesh/ready label 2026-10-16 21:39:55 +00:00
mesh-tools commented 2026-10-16 21:39:55 +00:00
Author
Member
Copy Link
Copy Source

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now 78353ad272. Review it and mark that head with mesh-delivery.mark-ready, which writes label and comment in the order the forge counts.

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now 78353ad272a3cd091bf40a62202566682fb0d856. Review it and mark that head with `mesh-delivery.mark-ready`, which writes label and comment in the order the forge counts.
jschoubben commented 2026-10-16 21:45:38 +00:00
Owner
Copy Link
Copy Source

ready at 78353ad272

ready at 78353ad272a3cd091bf40a62202566682fb0d856
jschoubben added the mesh/ready label 2026-10-16 21:50:51 +00:00
mesh-tools removed the mesh/ready label 2026-10-16 21:51:57 +00:00
mesh-tools commented 2026-10-16 21:51:57 +00:00
Author
Member
Copy Link
Copy Source

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now 78353ad272. Review it and mark that head with mesh-delivery.mark-ready, which writes label and comment in the order the forge counts.

mesh-delivery: the label mesh/ready is taken off: no "ready at" comment by a listed account follows both the label's last addition and the last push; the head is now 78353ad272a3cd091bf40a62202566682fb0d856. Review it and mark that head with `mesh-delivery.mark-ready`, which writes label and comment in the order the forge counts.
jschoubben added the mesh/ready label 2026-10-16 21:52:03 +00:00
jschoubben commented 2026-10-16 21:52:28 +00:00
Owner
Copy Link
Copy Source

ready at 78353ad272

ready at 78353ad272a3cd091bf40a62202566682fb0d856
mesh-tools merged commit 73b9cc3257 into main 2026-10-16 21:56:25 +00:00
mesh-tools deleted branch fix/957-playbook-08-first-fill 2026-10-16 21:56:25 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels mesh/ready
Milestone
No items
No Milestone
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#391