novox/mesh-controller
Archived
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Say a pull request the forge never announced as one, with what to do (hq issue 347) #178

Merged
mesh-admin merged 2 commits from fix/347-an-unannounced-pull-request-says-what-to-do into main 2026-10-09 11:38:48 +00:00
Conversation 2 Commits 2 Files Changed 2
+36
mesh-admin commented 2026-10-09 11:16:50 +00:00
Contributor
Copy Link
Copy Source

hq issue 347 (hq #247); pairs with mesh-catalog #159.

mesh-delivery (in #159) says an open pull request on a base requiring the merge check, with none on its head for ten minutes, as a stalled line in state unannounced; D14 raises it as delivery.<id>.stalled. No delivery exists for it, so stalledWords' generic needs (stop it, release it) named an act that does not apply. For state unannounced it now says: "A pull request of has had no merge check for

Test TestAnUnannouncedPullRequestSaysToPushANewCommit fails before (it said "stop it from the mesh MCP server") and passes after. merge-check.sh (race, full suite) passes locally on main + this.

Not merged. Merge before or with mesh-catalog #159.

hq issue 347 (hq #247); pairs with mesh-catalog #159. mesh-delivery (in #159) says an open pull request on a base requiring the merge check, with none on its head for ten minutes, as a `stalled` line in state `unannounced`; D14 raises it as `delivery.<id>.stalled`. No delivery exists for it, so `stalledWords`' generic needs (stop it, release it) named an act that does not apply. For state `unannounced` it now says: "A pull request of <repo> has had no merge check for <time>", why (the forge never announced it; it cannot merge until checked), and needs "push a new commit to its branch; the forge announces it and the mesh checks it". No actions (nothing a notification click can do). Test `TestAnUnannouncedPullRequestSaysToPushANewCommit` fails before (it said "stop it from the mesh MCP server") and passes after. `merge-check.sh` (race, full suite) passes locally on main + this. Not merged. Merge before or with mesh-catalog #159.
mesh-admin added 1 commit 2026-10-09 11:16:50 +00:00
Say a pull request the forge never announced as one, with what to do (hq issue 347) 510c91f144 
mesh-delivery now says a pull request on a base that requires the merge
check, with none on its head for ten minutes, as a stalled line in state
unannounced, which D14 raises as delivery.<id>.stalled. No delivery exists
for it, so the generic words — stop it, release it — named an act that
does not apply. It now says the pull request has had no merge check, why,
and that a new commit on its branch is announced and checked.
jschoubben added 1 commit 2026-10-09 11:22:24 +00:00
Announce this head: the pull request was opened after its push, which the announcer misses (hq issue 347)
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
14ab2ddd9b
mesh-admin commented 2026-10-09 11:22:48 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-controller@14ab2ddd9b49 — delivered since 2026-10-09T11:59:10Z

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-controller
  • tier 1: build-agent
  • tier 2: route-proxy
  • ace: receives build-agent, route-proxy
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent, route-proxy
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • route-proxy provides route: its consumers are sent again after it
  • route-proxy keeps data (ADR 0233): what it holds is backed up before it moves

Machines

  • mesh-controller on novox: passed — healthy 3 times over 2m53s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 3m26s
  • build-agent on the rest running it: sent
  • route-proxy on ace: passed — healthy 3 times over 3m41s
  • route-proxy on the rest running it: sent

Transitions

  • 2026-10-09 11:22 (new) → proposed (announced): novox/mesh-controller#178's head announced
  • 2026-10-09 11:28 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 11:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 11:39 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 11:39 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
  • 2026-10-09 11:59 delivering → delivered (done): its walk is done: 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-controller@14ab2ddd9b49` — **delivered** since 2026-10-09T11:59:10Z **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - mesh-controller on novox: passed — healthy 3 times over 2m53s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m26s - build-agent on the rest running it: sent - route-proxy on ace: passed — healthy 3 times over 3m41s - route-proxy on the rest running it: sent **Transitions** - 2026-10-09 11:22 (new) → proposed (announced): novox/mesh-controller#178's head announced - 2026-10-09 11:28 proposed → checked (checked): the verdict names this commit - 2026-10-09 11:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 11:39 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 11:39 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 - 2026-10-09 11:59 delivering → delivered (done): its walk is done: 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-admin commented 2026-10-09 11:28:13 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 14ab2ddd

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
  • mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-controller
  • tier 1: build-agent
  • tier 2: route-proxy
  • ace: receives build-agent, route-proxy
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent, route-proxy
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • route-proxy provides route: its consumers are sent again after it
  • route-proxy keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791544966285058886 (builds --log build-1791544966285058886).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:16:23Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T11:16:23Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-controller/cmd/mesh-builder	1.035s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	191.241s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.008s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.012s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.008s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.193s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.042s
ok  	github.com/novox/mesh-controller/internal/broker	2.897s
ok  	github.com/novox/mesh-controller/internal/builder	2.455s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.271s
ok  	github.com/novox/mesh-controller/internal/conditions	2.323s
ok  	github.com/novox/mesh-controller/internal/envfile	1.027s
ok  	github.com/novox/mesh-controller/internal/facts	1.030s
ok  	github.com/novox/mesh-controller/internal/identity	4.422s
ok  	github.com/novox/mesh-controller/internal/inventory	70.997s
ok  	github.com/novox/mesh-controller/internal/lease	17.710s
ok  	github.com/novox/mesh-controller/internal/licences	4.052s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.009s
ok  	github.com/novox/mesh-controller/internal/link	50.989s
ok  	github.com/novox/mesh-controller/internal/lint	1.847s
ok  	github.com/novox/mesh-controller/internal/outward	1.033s
ok  	github.com/novox/mesh-controller/internal/overlay	1.018s
ok  	github.com/novox/mesh-controller/internal/secrets	1.374s
ok  	github.com/novox/mesh-controller/internal/store	3.295s
ok  	github.com/novox/mesh-controller/internal/testbus	1.163s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
**Merge check** at `14ab2ddd` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791544966285058886` (`builds --log build-1791544966285058886`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:16:23Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-09T11:16:23Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-controller/cmd/mesh-builder 1.035s ok github.com/novox/mesh-controller/cmd/mesh-controller 191.241s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.008s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.012s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.008s ok github.com/novox/mesh-controller/examples/route-proxy 1.193s ok github.com/novox/mesh-controller/internal/artifacts 1.042s ok github.com/novox/mesh-controller/internal/broker 2.897s ok github.com/novox/mesh-controller/internal/builder 2.455s ok github.com/novox/mesh-controller/internal/catalogue 4.271s ok github.com/novox/mesh-controller/internal/conditions 2.323s ok github.com/novox/mesh-controller/internal/envfile 1.027s ok github.com/novox/mesh-controller/internal/facts 1.030s ok github.com/novox/mesh-controller/internal/identity 4.422s ok github.com/novox/mesh-controller/internal/inventory 70.997s ok github.com/novox/mesh-controller/internal/lease 17.710s ok github.com/novox/mesh-controller/internal/licences 4.052s ok github.com/novox/mesh-controller/internal/licences/adapters 1.009s ok github.com/novox/mesh-controller/internal/link 50.989s ok github.com/novox/mesh-controller/internal/lint 1.847s ok github.com/novox/mesh-controller/internal/outward 1.033s ok github.com/novox/mesh-controller/internal/overlay 1.018s ok github.com/novox/mesh-controller/internal/secrets 1.374s ok github.com/novox/mesh-controller/internal/store 3.295s ok github.com/novox/mesh-controller/internal/testbus 1.163s ok github.com/novox/mesh-controller/internal/token 1.015s ```
mesh-admin merged commit 63e85b25e6 into main 2026-10-09 11:38:48 +00:00
mesh-admin deleted branch fix/347-an-unannounced-pull-request-says-what-to-do 2026-10-09 11:38:48 +00:00
This repo is archived. You cannot comment on pull requests.
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
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#178