Say an unanswered merge check in its own words, with no action it cannot take (issue 438) #213

Merged
mesh-admin merged 2 commits from fix/438-a-check-that-never-answered-is-said into main 2026-10-11 00:47:11 +00:00
Contributor

novox/hq issue 438 (the watch counts pending as checked). The controller half of the fix; the other half is novox/mesh-catalog#195 (mesh-delivery and gitea), on the same branch name, so the two are one delivery group. This one merges first: #195 declares after: novox/mesh-controller.

What was wrong. With #195, mesh-delivery says a pull request's head whose merge check started and never answered as a stalled line in the state unanswered. stalledWords had words of its own only for unannounced; any other state took the generic delivery words, so the operator would read "Delivery of mesh-controller unanswered for 61 minutes" with a Stop button. mesh-delivery.stop refuses it, because no delivery of that head exists.

What changes.

  • stalledLine reads the line's new waiting field: the checks waited on, as mesh-delivery says each (mesh/merge-gate pending since <UTC time>, mesh/repo-check never set).
  • unansweredWords gives the state its own words, in the same form as the unannounced words. It offers no action. The operator can push a new commit, which asks the check again, or look at the build queue (mesh-controller.queue).
  • A line without waiting (a mesh-delivery from before #195) still gets these words, without the list of checks.
  • The unannounced words are unchanged: they are right for a head with no merge check at all.

For the line mesh-delivery produces, the operator reads:

  • Headline: Pull request mesh-controller #212's merge check has not answered for 61 minutes
  • Explanation: Pull request mesh-controller #212 is open on a branch that requires the merge check. Its merge check (mesh/merge-gate pending since 2026-10-11T00:11:39Z, mesh/repo-check never set) was asked and has not answered for 61 minutes, past its limit of 60 minutes. It cannot merge until its check answers.
  • Needs you: push a new commit to its branch, which asks the check again, or see whether its check still waits in the build queue: mesh-controller.queue.
  • Resolved: Pull request mesh-controller #212 has an answer from its merge check, or is closed

The word. unanswered is proposed for the glossary and is not in it yet. No word in the delivery table or the glossary fits a head that was announced but has no delivery held. unheld already means a waiting walk no delivery holds. unanswered comes from the table's own words for the proposed state's bound: "its check was asked and not answered".

What I checked.

  • TestAnUnansweredMergeCheckSaysWhichCheckAndWhatToDo decodes the exact line that #195's test logs. On main it fails for the intended reason: the generic headline "Delivery of mesh-controller unanswered for 61 minutes" and a Stop action. It passes with this change.
  • go vet ./... and go test ./cmd/mesh-controller/ -count=1 pass. TestTheServiceManagerReadsTheSystemdRenderingAsMeant (issue 432) also passed on this workstation.
  • The review's two word fixes are in 671e350: "the build queue" (the glossary's word for the controller's queue; the build seat does not hold it), and a headline naming the merge check as the pair.

What I did not verify. I did not run make check, so the store-backed tests were not run; this change touches no store. I have not seen the words in a real notification.

novox/hq issue 438 (the watch counts pending as checked). The controller half of the fix; the other half is novox/mesh-catalog#195 (mesh-delivery and gitea), on the same branch name, so the two are one delivery group. **This one merges first**: #195 declares `after: novox/mesh-controller`. **What was wrong.** With #195, mesh-delivery says a pull request's head whose merge check started and never answered as a `stalled` line in the state `unanswered`. `stalledWords` had words of its own only for `unannounced`; any other state took the generic delivery words, so the operator would read "Delivery of mesh-controller unanswered for 61 minutes" with a **Stop** button. `mesh-delivery.stop` refuses it, because no delivery of that head exists. **What changes.** - `stalledLine` reads the line's new `waiting` field: the checks waited on, as mesh-delivery says each (`mesh/merge-gate pending since <UTC time>`, `mesh/repo-check never set`). - `unansweredWords` gives the state its own words, in the same form as the `unannounced` words. It offers no action. The operator can push a new commit, which asks the check again, or look at the build queue (`mesh-controller.queue`). - A line without `waiting` (a mesh-delivery from before #195) still gets these words, without the list of checks. - The `unannounced` words are unchanged: they are right for a head with no merge check at all. For the line mesh-delivery produces, the operator reads: - Headline: Pull request mesh-controller #212's merge check has not answered for 61 minutes - Explanation: Pull request mesh-controller #212 is open on a branch that requires the merge check. Its merge check (mesh/merge-gate pending since 2026-10-11T00:11:39Z, mesh/repo-check never set) was asked and has not answered for 61 minutes, past its limit of 60 minutes. It cannot merge until its check answers. - Needs you: push a new commit to its branch, which asks the check again, or see whether its check still waits in the build queue: mesh-controller.queue. - Resolved: Pull request mesh-controller #212 has an answer from its merge check, or is closed **The word.** `unanswered` is proposed for the glossary and is not in it yet. No word in the delivery table or the glossary fits a head that was announced but has no delivery held. `unheld` already means a waiting walk no delivery holds. `unanswered` comes from the table's own words for the proposed state's bound: "its check was asked and not answered". **What I checked.** - `TestAnUnansweredMergeCheckSaysWhichCheckAndWhatToDo` decodes the exact line that #195's test logs. On main it fails for the intended reason: the generic headline "Delivery of mesh-controller unanswered for 61 minutes" and a Stop action. It passes with this change. - `go vet ./...` and `go test ./cmd/mesh-controller/ -count=1` pass. `TestTheServiceManagerReadsTheSystemdRenderingAsMeant` (issue 432) also passed on this workstation. - The review's two word fixes are in 671e350: "the build queue" (the glossary's word for the controller's queue; the build seat does not hold it), and a headline naming the merge check as the pair. **What I did not verify.** I did not run `make check`, so the store-backed tests were not run; this change touches no store. I have not seen the words in a real notification.
mesh-admin added 1 commit 2026-10-11 00:25:25 +00:00
Say an unanswered merge check in its own words, with no action it cannot take (issue 438)
mesh/delivery-group group fix/438-a-check-that-never-answered-is-said checking: 0 of 2 member(s) ready
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds mesh-controller → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
585caa4371
mesh-delivery now says a head whose merge check started and never answered as a
stalled line in state unanswered. Through the generic delivery words it would read
as a delivery and offer a Stop that mesh-delivery refuses, since no delivery of
the head exists; it now names the checks waited on and what the operator can do.
Author
Contributor

Delivery novox/mesh-controller@671e350f56e3 — delivered since 2026-10-11T00:54:02Z

Delivery plan — builds mesh-controller → novox; no bus step

  • tier 0: mesh-controller
  • novox: receives mesh-controller

Group fix/438-a-check-that-never-answered-is-said, in order: novox/mesh-controller@671e350f56 → novox/mesh-catalog@450892498d

Machines

  • gitea on novox: passed — healthy 3 times over 3m39s
  • mesh-controller on novox: passed — judged with gitea: healthy 3 times over 3m39s
  • mesh-delivery on novox: passed — judged with gitea: healthy 3 times over 3m39s
  • gitea on the rest running it: sent
  • mesh-controller on the rest running it: sent
  • mesh-delivery on the rest running it: sent

Transitions

  • 2026-10-11 00:30 (new) → proposed (announced): novox/mesh-controller#213's head announced
  • 2026-10-11 00:37 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 00:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 00:49 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-11 00:49 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-11 00:54 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-controller@671e350f56e3` — **delivered** since 2026-10-11T00:54:02Z **Delivery plan** — builds mesh-controller → novox; no bus step - tier 0: mesh-controller - novox: receives mesh-controller **Group** `fix/438-a-check-that-never-answered-is-said`, in order: novox/mesh-controller@671e350f56e3 → novox/mesh-catalog@450892498d1d - novox/mesh-controller@671e350f56e3 before novox/mesh-catalog@450892498d1d: declared - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - gitea on novox: passed — healthy 3 times over 3m39s - mesh-controller on novox: passed — judged with gitea: healthy 3 times over 3m39s - mesh-delivery on novox: passed — judged with gitea: healthy 3 times over 3m39s - gitea on the rest running it: sent - mesh-controller on the rest running it: sent - mesh-delivery on the rest running it: sent **Transitions** - 2026-10-11 00:30 (new) → proposed (announced): novox/mesh-controller#213's head announced - 2026-10-11 00:37 proposed → checked (checked): the verdict names this commit - 2026-10-11 00:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 00:49 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-11 00:49 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-11 00:54 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`.
jschoubben added 1 commit 2026-10-11 00:30:22 +00:00
Name the build queue and the merge check as the glossary does (issue 438)
mesh/merge-gate pass: builds mesh-controller → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
mesh/delivery-group group fix/438-a-check-that-never-answered-is-said merged: every member is merged
671e350f56
Review of #213: the queue is the controller's build queue, not the build seat's,
and the merge check is the pair, so the headline says the pull request's merge
check has not answered.
Author
Contributor

Merge check at 585caa43

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

Delivery plan — builds mesh-controller → novox; no bus step

  • tier 0: mesh-controller
  • novox: receives mesh-controller
  • read by no module's build: cmd/mesh-controller/plain_words_test.go

Run by the build seat on shanks as build-1791678356415314529 (builds --log build-1791678356415314529).

--- the gate: mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); 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: 1
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T00:24:56Z 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-11T00:24:56Z

modules the change moves:
  - mesh-controller (changed)

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 1 module(s) in 1 tier(s): mesh-controller

notes:
  - cmd/mesh-controller/plain_words_test.go read by no module's build, and rebuild nothing (issue 280)
--- 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	250.132s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.048s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.064s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.048s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.255s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.087s
ok  	github.com/novox/mesh-controller/internal/broker	2.854s
ok  	github.com/novox/mesh-controller/internal/builder	2.813s
ok  	github.com/novox/mesh-controller/internal/catalogue	6.091s
ok  	github.com/novox/mesh-controller/internal/conditions	2.616s
ok  	github.com/novox/mesh-controller/internal/envfile	1.047s
ok  	github.com/novox/mesh-controller/internal/facts	1.066s
ok  	github.com/novox/mesh-controller/internal/identity	5.464s
ok  	github.com/novox/mesh-controller/internal/inventory	99.642s
ok  	github.com/novox/mesh-controller/internal/lease	17.655s
ok  	github.com/novox/mesh-controller/internal/licences	4.758s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.047s
ok  	github.com/novox/mesh-controller/internal/link	54.967s
ok  	github.com/novox/mesh-controller/internal/lint	2.377s
ok  	github.com/novox/mesh-controller/internal/outward	1.088s
ok  	github.com/novox/mesh-controller/internal/overlay	1.076s
ok  	github.com/novox/mesh-controller/internal/secrets	1.554s
ok  	github.com/novox/mesh-controller/internal/store	3.505s
ok  	github.com/novox/mesh-controller/internal/testbus	1.245s
ok  	github.com/novox/mesh-controller/internal/token	1.017s
**Merge check** at `585caa43` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-controller → novox; no bus step - tier 0: mesh-controller - novox: receives mesh-controller - read by no module's build: cmd/mesh-controller/plain_words_test.go Run by the build seat on shanks as `build-1791678356415314529` (`builds --log build-1791678356415314529`). ``` --- the gate: mesh-controller mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); 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: 1 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T00:24:56Z 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-11T00:24:56Z modules the change moves: - mesh-controller (changed) 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 1 module(s) in 1 tier(s): mesh-controller notes: - cmd/mesh-controller/plain_words_test.go read by no module's build, and rebuild nothing (issue 280) --- 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 250.132s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.048s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.064s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.048s ok github.com/novox/mesh-controller/examples/route-proxy 1.255s ok github.com/novox/mesh-controller/internal/artifacts 1.087s ok github.com/novox/mesh-controller/internal/broker 2.854s ok github.com/novox/mesh-controller/internal/builder 2.813s ok github.com/novox/mesh-controller/internal/catalogue 6.091s ok github.com/novox/mesh-controller/internal/conditions 2.616s ok github.com/novox/mesh-controller/internal/envfile 1.047s ok github.com/novox/mesh-controller/internal/facts 1.066s ok github.com/novox/mesh-controller/internal/identity 5.464s ok github.com/novox/mesh-controller/internal/inventory 99.642s ok github.com/novox/mesh-controller/internal/lease 17.655s ok github.com/novox/mesh-controller/internal/licences 4.758s ok github.com/novox/mesh-controller/internal/licences/adapters 1.047s ok github.com/novox/mesh-controller/internal/link 54.967s ok github.com/novox/mesh-controller/internal/lint 2.377s ok github.com/novox/mesh-controller/internal/outward 1.088s ok github.com/novox/mesh-controller/internal/overlay 1.076s ok github.com/novox/mesh-controller/internal/secrets 1.554s ok github.com/novox/mesh-controller/internal/store 3.505s ok github.com/novox/mesh-controller/internal/testbus 1.245s ok github.com/novox/mesh-controller/internal/token 1.017s ```
Author
Contributor

Merge check at 671e350f

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

Delivery plan — builds mesh-controller → novox; no bus step

  • tier 0: mesh-controller
  • novox: receives mesh-controller
  • read by no module's build: cmd/mesh-controller/plain_words_test.go

Run by the build seat on novox as build-1791678629805730087 (builds --log build-1791678629805730087).

--- the gate: mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); 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: 1
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T00:24:56Z 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-11T00:24:56Z

modules the change moves:
  - mesh-controller (changed)

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 1 module(s) in 1 tier(s): mesh-controller

notes:
  - cmd/mesh-controller/plain_words_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-controller/cmd/mesh-builder	1.033s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	272.181s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.021s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.030s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.022s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.136s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.060s
ok  	github.com/novox/mesh-controller/internal/broker	5.651s
ok  	github.com/novox/mesh-controller/internal/builder	11.288s
ok  	github.com/novox/mesh-controller/internal/catalogue	5.242s
ok  	github.com/novox/mesh-controller/internal/conditions	2.573s
ok  	github.com/novox/mesh-controller/internal/envfile	1.028s
ok  	github.com/novox/mesh-controller/internal/facts	1.032s
ok  	github.com/novox/mesh-controller/internal/identity	9.719s
ok  	github.com/novox/mesh-controller/internal/inventory	111.778s
ok  	github.com/novox/mesh-controller/internal/lease	17.692s
ok  	github.com/novox/mesh-controller/internal/licences	9.142s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.007s
ok  	github.com/novox/mesh-controller/internal/link	56.654s
ok  	github.com/novox/mesh-controller/internal/lint	2.250s
ok  	github.com/novox/mesh-controller/internal/outward	1.032s
ok  	github.com/novox/mesh-controller/internal/overlay	1.028s
ok  	github.com/novox/mesh-controller/internal/secrets	1.429s
ok  	github.com/novox/mesh-controller/internal/store	5.867s
ok  	github.com/novox/mesh-controller/internal/testbus	1.182s
ok  	github.com/novox/mesh-controller/internal/token	1.012s
**Merge check** at `671e350f` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-controller → novox; no bus step - tier 0: mesh-controller - novox: receives mesh-controller - read by no module's build: cmd/mesh-controller/plain_words_test.go Run by the build seat on novox as `build-1791678629805730087` (`builds --log build-1791678629805730087`). ``` --- the gate: mesh-controller mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); 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: 1 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T00:24:56Z 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-11T00:24:56Z modules the change moves: - mesh-controller (changed) 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 1 module(s) in 1 tier(s): mesh-controller notes: - cmd/mesh-controller/plain_words_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-controller/cmd/mesh-builder 1.033s ok github.com/novox/mesh-controller/cmd/mesh-controller 272.181s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.021s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.030s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.022s ok github.com/novox/mesh-controller/examples/route-proxy 1.136s ok github.com/novox/mesh-controller/internal/artifacts 1.060s ok github.com/novox/mesh-controller/internal/broker 5.651s ok github.com/novox/mesh-controller/internal/builder 11.288s ok github.com/novox/mesh-controller/internal/catalogue 5.242s ok github.com/novox/mesh-controller/internal/conditions 2.573s ok github.com/novox/mesh-controller/internal/envfile 1.028s ok github.com/novox/mesh-controller/internal/facts 1.032s ok github.com/novox/mesh-controller/internal/identity 9.719s ok github.com/novox/mesh-controller/internal/inventory 111.778s ok github.com/novox/mesh-controller/internal/lease 17.692s ok github.com/novox/mesh-controller/internal/licences 9.142s ok github.com/novox/mesh-controller/internal/licences/adapters 1.007s ok github.com/novox/mesh-controller/internal/link 56.654s ok github.com/novox/mesh-controller/internal/lint 2.250s ok github.com/novox/mesh-controller/internal/outward 1.032s ok github.com/novox/mesh-controller/internal/overlay 1.028s ok github.com/novox/mesh-controller/internal/secrets 1.429s ok github.com/novox/mesh-controller/internal/store 5.867s ok github.com/novox/mesh-controller/internal/testbus 1.182s ok github.com/novox/mesh-controller/internal/token 1.012s ```
mesh-admin merged commit 11ffab887b into main 2026-10-11 00:47:11 +00:00
mesh-admin deleted branch fix/438-a-check-that-never-answered-is-said 2026-10-11 00:47:11 +00:00
This repo is archived. You cannot comment on pull requests.
No Reviewers
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#213