The provisioner follows the one rule for provisions, and the gate says a group's members when they change (issue 774) #572

Merged

mesh-tools merged 2 commits from fix/one-rule-for-provisions into main 2026-10-30 22:33:52 +00:00

Conversation 1 Commits 2 Files Changed 5

+59 -5

mesh-tools commented 2026-10-30 21:32:39 +00:00

Member

Copy Link

Copy Source

mesh-provisioner pins mesh-sdk 6c5a8ef (the one rule), so it keys route-only plans for modules not yet moved. Also fdd18331: mesh-delivery-gate writes mesh/delivery-group again when a group's why line or member set changes (a joining member had no status and the others kept "3 of 3"); TestAGroupSaysAJoiningMember.

Group fix/one-rule-for-provisions (mesh-sdk, mesh-delivery, mesh-catalog), issue 774 and L6 (issue 1954). The lead merges once mesh/check and mesh/delivery-group are green AND mesh-catalog #570 (the provisioner client takes a plan with no templates) has reached every node: this group's mesh-provisioner writes route-only plans the old client would report failed. mesh-sdk first.
Reviewed-by: rev-sweep@shanks at 843c1c337c

mesh-provisioner pins mesh-sdk 6c5a8ef (the one rule), so it keys route-only plans for modules not yet moved. Also fdd18331: mesh-delivery-gate writes mesh/delivery-group again when a group's why line or member set changes (a joining member had no status and the others kept "3 of 3"); TestAGroupSaysAJoiningMember. Group fix/one-rule-for-provisions (mesh-sdk, mesh-delivery, mesh-catalog), issue 774 and L6 (issue 1954). The lead merges once mesh/check and mesh/delivery-group are green AND mesh-catalog #570 (the provisioner client takes a plan with no templates) has reached every node: this group's mesh-provisioner writes route-only plans the old client would report failed. mesh-sdk first. Reviewed-by: rev-sweep@shanks at 843c1c337cddefd8f53899948c53285eb2cb72eb

mesh-tools added 2 commits 2026-10-30 21:32:39 +00:00

The gate says a group again when a member joins, leaves or pushes, or its why changes, so the forge never shows a stale member count (issue 774) ... fdd1833143

On 2026-10-30 mesh-catalog #571 joined fix/held-module-and-assigner-contract at 21:59; the group stayed
checking, so mesh/delivery-group kept saying "3 of 3 member(s) ready" for a group of four, and #571 had
no mesh/delivery-group status until the state changed.

Quick fix: compare the why too. Thorough fix: compare the why and the member ids (each names its head),
so a push that keeps the count is said as well. Chose thorough: same size, covers the push case.

Compose plans with mesh-sdk 6c5a8ef893b4, the one rule of what is keyed (issue 774) ... 843c1c337c

A module not handed now has a plan for what a provider's helper answers of it, so grafana's route is keyed and
route-proxy's helper hears it; handed modules' plans are unchanged. Deliver after #570, whose client reads a plan with
no templates.

mesh-tools commented 2026-10-30 21:32:47 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@843c1c337cdd — merged since 2026-10-30T22:33:54Z

Source — source.main moved to novox/mesh-catalog@5be46a80cb. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group fix/one-rule-for-provisions: novox/mesh-catalog@843c1c337c, novox/mesh-delivery@6298d9d67c, novox/mesh-sdk@6c5a8ef893

• composed together: pass — the checker's verdict at the members' heads (c3131640479a)

Transitions

• 2026-10-30 21:32 (new) → proposed (announced): novox/mesh-catalog#572's head announced
• 2026-10-30 21:32 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
• 2026-10-30 22:33 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@843c1c337cdd` — **merged** since 2026-10-30T22:33:54Z **Source** — source.main moved to novox/mesh-catalog@5be46a80cb35. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/one-rule-for-provisions`: novox/mesh-catalog@843c1c337cdd, novox/mesh-delivery@6298d9d67c83, novox/mesh-sdk@6c5a8ef893b4 - composed together: pass — the checker's verdict at the members' heads (c3131640479a) **Transitions** - 2026-10-30 21:32 (new) → proposed (announced): novox/mesh-catalog#572's head announced - 2026-10-30 21:32 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-30 22:33 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 5be46a80cb into main 2026-10-30 22:33:52 +00:00

mesh-tools deleted branch fix/one-rule-for-provisions 2026-10-30 22:33:52 +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#572