novox/mesh-catalog
13
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Readers of the assignments skip an ended or pending one (design 47 milestone 5, issue 1098) #357

Merged
mesh-tools merged 6 commits from feat/chain-on-the-bus into main 2026-10-18 02:04:17 +00:00
Conversation 3 Commits 6 Files Changed 18
+236 -31
mesh-tools commented 2026-10-18 01:39:27 +00:00
Member
Copy Link
Copy Source

Design 47 milestone 5, delivery 1 (issue 1098; ADR 0408 §4): every reader of the controller's assignments bucket treats a value with ended or a non-empty state exactly as a removed key, and reads the new link fields without a change of key.

  • mesh-config, mesh-vault and mesh-provisioner-client skip an ended or pending assignment. mesh-config and mesh-vault keep a local copy of the check (issue 1100).
  • gitea, postgres, keycloak, route-adapter and mesh-provisioner-client take mesh-sdk f185aed (provider.Standing).
  • The guard test that the bus's storage stays declared with a backup (ADR 0408 §7) was taken out of modules/nats. A file there makes the delivery move the bus, which waits for a person's bus upgrade. It follows as a repository check in issue 1104.

One delivery group with mesh-controller and mesh-sdk (branch feat/chain-on-the-bus).

Reviewed-by: reviewer-chain@shanks at 3bc4215d87

Design 47 milestone 5, delivery 1 (issue 1098; ADR 0408 §4): every reader of the controller's assignments bucket treats a value with `ended` or a non-empty `state` exactly as a removed key, and reads the new link fields without a change of key. - mesh-config, mesh-vault and mesh-provisioner-client skip an ended or pending assignment. mesh-config and mesh-vault keep a local copy of the check (issue 1100). - gitea, postgres, keycloak, route-adapter and mesh-provisioner-client take mesh-sdk f185aed (provider.Standing). - The guard test that the bus's storage stays declared with a backup (ADR 0408 §7) was taken out of modules/nats. A file there makes the delivery move the bus, which waits for a person's bus upgrade. It follows as a repository check in issue 1104. One delivery group with mesh-controller and mesh-sdk (branch feat/chain-on-the-bus). Reviewed-by: reviewer-chain@shanks at 3bc4215d872c052bce4af4ce1afc196707bd8e5c
mesh-tools added 5 commits 2026-10-18 01:39:27 +00:00
mesh-config drops an ended assignment as a removed one (issue 1098) bdbca4b921
mesh-vault reads an ended assignment as a removed key (issue 1098) 60a3823f0e
mesh-provisioner-client takes a module off the node when its assignment is ended (issue 1098) 9edd16eaeb
Guard that the bus storage stays declared as data with a backup (issue 1098) 84af0ed180
Providers and the provisioner client take the SDK that reads an ended assignment as a removed key (issue 1098)
mesh/repo-check head 68e3326d4cbc merged into trunk 44e7002d3c84 beside mesh-controller#378@b56c1d00 — pass: its merge-check.sh passed, each part in its to…
Details
mesh/delivery-group group feat/chain-on-the-bus ready: every member ready, and composed together they pass
Details
mesh/merge-gate head 68e3326d4cbc merged into trunk 44e7002d3c84 — pass: group feat/chain-on-the-bus composed: every machine composes with the change as it…
Details
mesh/delivery superseded: a newer head of the same pull request
Details
68e3326d4c
mesh-tools commented 2026-10-18 01:39:32 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@3bc4215d872c — stopped since 2026-10-18T09:00:28Z

Delivery plan — builds gitea, keycloak, mesh-config, mesh-provisioner-client, mesh-vault, postgres, route-adapter → ace, g14, novox, shanks; no bus step; 3 wait(s) for a person

  • tier 0: gitea, keycloak, mesh-config, mesh-provisioner-client, mesh-vault, postgres, route-adapter
  • ace: receives mesh-provisioner-client; waits for a person: postgres
  • g14: receives mesh-provisioner-client
  • novox: receives gitea, mesh-config, mesh-provisioner-client, mesh-vault; waits for a person: keycloak, postgres
  • shanks: receives 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
  • keycloak 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
  • keycloak provides oidc-client: its consumers are sent again after it
  • keycloak keeps data (ADR 0233): what it holds is backed up before it moves
  • mesh-vault provides secret: its consumers are sent again after it
  • mesh-vault keeps data (ADR 0233): what it holds is backed up before it moves
  • postgres 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
  • postgres provides postgres-database: its consumers are sent again after it
  • postgres 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-provisioner-client is judged on its first machine

Group feat/chain-on-the-bus: novox/mesh-catalog@3bc4215d87, novox/mesh-controller@0149a3d7de, novox/mesh-sdk@f185aedbf5

Transitions

  • 2026-10-18 01:56 (new) → proposed (announced): novox/mesh-catalog#357's head announced
  • 2026-10-18 01:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-18 01:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-18 02:43 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-18 09:00 published → stopped (stop): its walk plan-1792289060772890935 was stopped by a person (mesh-controller): the operator, via telegram (user id verified), chose Stop (ask c6d5dc209840802c0)

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@3bc4215d872c` — **stopped** since 2026-10-18T09:00:28Z **Delivery plan** — builds gitea, keycloak, mesh-config, mesh-provisioner-client, mesh-vault, postgres, route-adapter → ace, g14, novox, shanks; no bus step; 3 wait(s) for a person - tier 0: gitea, keycloak, mesh-config, mesh-provisioner-client, mesh-vault, postgres, route-adapter - ace: receives mesh-provisioner-client; waits for a person: postgres - g14: receives mesh-provisioner-client - novox: receives gitea, mesh-config, mesh-provisioner-client, mesh-vault; waits for a person: keycloak, postgres - shanks: receives 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 - keycloak 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 - keycloak provides oidc-client: its consumers are sent again after it - keycloak keeps data (ADR 0233): what it holds is backed up before it moves - mesh-vault provides secret: its consumers are sent again after it - mesh-vault keeps data (ADR 0233): what it holds is backed up before it moves - postgres 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 - postgres provides postgres-database: its consumers are sent again after it - postgres 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-provisioner-client is judged on its first machine **Group** `feat/chain-on-the-bus`: novox/mesh-catalog@3bc4215d872c, novox/mesh-controller@0149a3d7de20, novox/mesh-sdk@f185aedbf5d6 **Transitions** - 2026-10-18 01:56 (new) → proposed (announced): novox/mesh-catalog#357's head announced - 2026-10-18 01:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 01:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 02:43 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 09:00 published → stopped (stop): its walk plan-1792289060772890935 was stopped by a person (mesh-controller): the operator, via telegram (user id verified), chose Stop (ask c6d5dc209840802c0) The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-10-18 01:56:15 +00:00
Take the bus's backup guard out of modules/nats: it would move the bus (issue 1098, guard follows in issue 1104)
mesh/repo-check head 3bc4215d872c merged into trunk 44e7002d3c84 beside mesh-controller#378@0149a3d7 — pass: its merge-check.sh passed, each part in its to…
Details
mesh/delivery stopped: its walk plan-1792289060772890935 was stopped by a person (mesh-controller): the operator, via telegram (user id verified), chose …
Details
mesh/delivery-group group feat/chain-on-the-bus stopped: a member was stopped
Details
mesh/merge-gate out of date: judged against trunk 798d6fd68589, the trunk is now e40ec47058e6; judged again on a recheck or when it is merged
Details
3bc4215d87
mesh-tools commented 2026-10-18 01:56:20 +00:00
Author
Member
Copy Link
Copy Source

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-tools merged commit d3dd46a9fd into main 2026-10-18 02:04:17 +00:00
mesh-tools deleted branch feat/chain-on-the-bus 2026-10-18 02:04:17 +00:00
mesh-tools commented 2026-10-18 09:26:29 +00:00
Author
Member
Copy Link
Copy Source

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#357