The checker runs beside today's check: build modules merge and place siblings; with automx, provisioner and gate fixes #423

Merged

mesh-tools merged 15 commits from feat/the-checker into main 2026-10-21 21:46:17 +00:00

Conversation 1 Commits 15 Files Changed 61

+2350 -522

mesh-tools commented 2026-10-21 20:24:13 +00:00

Member

Copy Link

Copy Source

Part of the milestone "The checker runs beside today's check" (design 47), one delivery group on feat/the-checker with mesh-sdk, mesh-delivery and mesh-controller.

The Go and Node build modules merge a pull request onto main for its check and report conflicts, changed files and module trees; siblings are placed beside the code; Go packages run in their own module. Riding in: automx as a Go program in a stock image; the provisioner client writes a file again when the node-engine's socket returns; xterm's defaults in the client's test fixtures; the merge gate no longer re-asks a group's SDK member without end.

Reviewed-by: reviewer-checker@shanks at 12ff1cfbc4

Part of the milestone "The checker runs beside today's check" (design 47), one delivery group on feat/the-checker with mesh-sdk, mesh-delivery and mesh-controller. The Go and Node build modules merge a pull request onto main for its check and report conflicts, changed files and module trees; siblings are placed beside the code; Go packages run in their own module. Riding in: automx as a Go program in a stock image; the provisioner client writes a file again when the node-engine's socket returns; xterm's defaults in the client's test fixtures; the merge gate no longer re-asks a group's SDK member without end. Reviewed-by: reviewer-checker@shanks at 12ff1cfbc434ac626d80e995e5b7221c3a2c2105

mesh-tools added 15 commits 2026-10-21 20:24:14 +00:00

Run mailu's automx as a Go program mounted into the mirrored alpine image, answering as captured but naming the IMAP server (issues 1631, 1632, 1700, 1701, ADR 0480) ... 70500c21a8

Python automx2, its database and its automx_rows tool go; the container keeps its name, network and port, gains an http health.

Make the build modules' fetch merge the head onto a trunk commit and place siblings beside the tree, so the checker judges the merge and tests read their siblings (issues 1675, 1676, 1677) d5804927b3

Build the merge preview's module trees with mesh-sdk's ModuleTrees and re-pin mesh-sdk to 78364e31, so the two fetch steps share it (issues 1675, 1676) aa0eaa6c52

Drop the unused imports from the Node fetch preview 33d8b71cf7

Drop the unused imports from the Node fetch preview 34b310b9f8

Fill again what failed for want of the node-engine's write socket, when inotify says the socket is back (issue 1165) 769a8d6f6a

Test the returning socket by a real restart of the stand-in node-engine aa5d263c08

Write a moved contributor's declared defaults into the provisioner client tests' stand-in mesh-config (issue 1780) 0cf7b2344f

Test that the integration level gets MESH_CHECK_BESIDE only when siblings were placed (issue 1677) 1319432e55

Merge remote-tracking branch 'origin/fix/xterm-config-defaults' into feat/the-checker 62e67578eb

Merge remote-tracking branch 'origin/fix/1165-fill-retry' into feat/the-checker ... d9876e5296

# Conflicts:
#	modules/mesh-provisioner-client/cmd/mesh-provisioner-client/client_test.go

Merge remote-tracking branch 'origin/feat/r4d-automx-go' into feat/the-checker ce72a366bf

Ask no check of a group member that waits on its composed check, and stop asking a merge refused the same way with no trunk move (issue 1106) 59b13d091d

Move the socket-return fill tests (issue 1165) to the integration level: they make a real socket and watch its directory 7bf0de0ff5

Merge remote-tracking branch 'origin/fix/1106-sdk-member-merges' into feat/the-checker 12ff1cfbc4

mesh-tools commented 2026-10-21 20:24:18 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@12ff1cfbc434 — delivered since 2026-10-21T22:16:29Z

Delivery plan — builds gitea, mailu, mesh-build-go, mesh-build-node, mesh-delivery-gate, mesh-provisioner-client → ace, g14, novox, shanks; no bus step; 1 wait(s) for a person

• tier 0: gitea, mailu, mesh-build-go, mesh-build-node, mesh-delivery-gate, mesh-provisioner-client
• ace: receives mesh-build-go, mesh-build-node, mesh-provisioner-client
• g14: receives mesh-build-go, mesh-build-node, mesh-provisioner-client
• novox: receives gitea, mesh-build-go, mesh-build-node, mesh-delivery-gate, mesh-provisioner-client; waits for a person: mailu
• shanks: receives mesh-build-go, mesh-build-node, mesh-provisioner-client
• gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it
• gitea keeps data (ADR 0233): what it holds is backed up before it moves
• mailu waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends
• mailu provides smtp: its consumers are sent again after it
• mailu keeps data (ADR 0233): what it holds is backed up before it moves
• grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-build-go, mesh-build-node, mesh-provisioner-client is judged on its first machine

Group feat/the-checker: novox/mesh-catalog@12ff1cfbc4, novox/mesh-controller@b9ec1919b8, novox/mesh-delivery@b519c8dde2, novox/mesh-sdk@580da61a91

• composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Machines

• mesh-build-go on every machine running it: sent
• mesh-build-node on every machine running it: sent
• mesh-controller on every machine running it: sent
• mesh-delivery-gate on every machine running it: sent
• mesh-provisioner-client on every machine running it: sent
• mesh-sdk on every machine running it: sent
• route-proxy on every machine running it: sent
• build-agent on every machine running it: sent
• mesh-delivery-builder on every machine running it: sent
• mesh-delivery-forge-bridge on every machine running it: sent
• mesh-delivery-indexer on every machine running it: sent
• mesh-tools on every machine running it: sent
• audit-logger on every machine running it: sent
• baserow on every machine running it: sent
• bazarr on every machine running it: sent
• bookshelf on every machine running it: sent
• confluence on every machine running it: sent
• gitea on every machine running it: sent
• gitlab on every machine running it: sent
• grafana on every machine running it: sent
• home-assistant on every machine running it: sent
• icecast on every machine running it: sent
• influxdb on every machine running it: sent
• jackett on every machine running it: sent
• jira on every machine running it: sent
• kometa on every machine running it: sent
• lab on every machine running it: sent
• letta on every machine running it: sent
• lidarr on every machine running it: sent
• mesh-catalog on every machine running it: sent
• model-usage on every machine running it: sent
• mosquitto on every machine running it: sent
• netcheck on every machine running it: sent
• nextcloud on every machine running it: sent
• nodered on every machine running it: sent
• ombi on every machine running it: sent
• openai-consumer on every machine running it: sent
• radarr on every machine running it: sent
• redis on every machine running it: sent
• route-adapter on every machine running it: sent
• searxng on every machine running it: sent
• showcase on every machine running it: sent
• sonarr on every machine running it: sent
• tautulli on every machine running it: sent
• umami on every machine running it: sent
• unifi on every machine running it: sent
• zsh on every machine running it: sent

Transitions

• 2026-10-21 20:24 (new) → proposed (announced): novox/mesh-catalog#423's head announced
• 2026-10-21 20:26 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-21 20:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-21 21:10 ready → proposed (recheck): issue 1792 met a second time: its mesh/repo-check went out of date at 22:45 when sibling mesh-sdk#66 moved to 580da61a, and nothing asked it again; the group cannot merge without it
• 2026-10-21 21:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-21 21:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-21 21:38 ready → proposed (trunk moved): out of date: judged against trunk 3793175894, the trunk is now f1fb73e12cee; judged again on a recheck or when it is merged
• 2026-10-21 21:41 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-21 21:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-21 21:48 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-21 21:48 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-21 22:16 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-catalog@12ff1cfbc434` — **delivered** since 2026-10-21T22:16:29Z **Delivery plan** — builds gitea, mailu, mesh-build-go, mesh-build-node, mesh-delivery-gate, mesh-provisioner-client → ace, g14, novox, shanks; no bus step; 1 wait(s) for a person - tier 0: gitea, mailu, mesh-build-go, mesh-build-node, mesh-delivery-gate, mesh-provisioner-client - ace: receives mesh-build-go, mesh-build-node, mesh-provisioner-client - g14: receives mesh-build-go, mesh-build-node, mesh-provisioner-client - novox: receives gitea, mesh-build-go, mesh-build-node, mesh-delivery-gate, mesh-provisioner-client; waits for a person: mailu - shanks: receives mesh-build-go, mesh-build-node, mesh-provisioner-client - gitea provides npm-package-registry, git, gitea-read, forge-account: its consumers are sent again after it - gitea keeps data (ADR 0233): what it holds is backed up before it moves - mailu waits for a person: its policy records (module) — unless on a machine its move recreates none of its containers and moves none of its data, which the walk judges and then sends - mailu provides smtp: its consumers are sent again after it - mailu keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-build-go, mesh-build-node, mesh-provisioner-client is judged on its first machine **Group** `feat/the-checker`: novox/mesh-catalog@12ff1cfbc434, novox/mesh-controller@b9ec1919b865, novox/mesh-delivery@b519c8dde2da, novox/mesh-sdk@580da61a9107 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-build-go on every machine running it: sent - mesh-build-node on every machine running it: sent - mesh-controller on every machine running it: sent - mesh-delivery-gate on every machine running it: sent - mesh-provisioner-client on every machine running it: sent - mesh-sdk on every machine running it: sent - route-proxy on every machine running it: sent - build-agent on every machine running it: sent - mesh-delivery-builder on every machine running it: sent - mesh-delivery-forge-bridge on every machine running it: sent - mesh-delivery-indexer on every machine running it: sent - mesh-tools on every machine running it: sent - audit-logger on every machine running it: sent - baserow on every machine running it: sent - bazarr on every machine running it: sent - bookshelf on every machine running it: sent - confluence on every machine running it: sent - gitea on every machine running it: sent - gitlab on every machine running it: sent - grafana on every machine running it: sent - home-assistant on every machine running it: sent - icecast on every machine running it: sent - influxdb on every machine running it: sent - jackett on every machine running it: sent - jira on every machine running it: sent - kometa on every machine running it: sent - lab on every machine running it: sent - letta on every machine running it: sent - lidarr on every machine running it: sent - mesh-catalog on every machine running it: sent - model-usage on every machine running it: sent - mosquitto on every machine running it: sent - netcheck on every machine running it: sent - nextcloud on every machine running it: sent - nodered on every machine running it: sent - ombi on every machine running it: sent - openai-consumer on every machine running it: sent - radarr on every machine running it: sent - redis on every machine running it: sent - route-adapter on every machine running it: sent - searxng on every machine running it: sent - showcase on every machine running it: sent - sonarr on every machine running it: sent - tautulli on every machine running it: sent - umami on every machine running it: sent - unifi on every machine running it: sent - zsh on every machine running it: sent **Transitions** - 2026-10-21 20:24 (new) → proposed (announced): novox/mesh-catalog#423's head announced - 2026-10-21 20:26 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 20:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 21:10 ready → proposed (recheck): issue 1792 met a second time: its mesh/repo-check went out of date at 22:45 when sibling mesh-sdk#66 moved to 580da61a, and nothing asked it again; the group cannot merge without it - 2026-10-21 21:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 21:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 21:38 ready → proposed (trunk moved): out of date: judged against trunk 379317589488, the trunk is now f1fb73e12cee; judged again on a recheck or when it is merged - 2026-10-21 21:41 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 21:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 21:48 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 21:48 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-21 22:16 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-tools merged commit f3100d1116 into main 2026-10-21 21:46:17 +00:00

mesh-tools deleted branch feat/the-checker 2026-10-21 21:46:17 +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

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#423