A build waits out a registry held still, and a retry asks every failed build of the tier (issue 457) #225

Merged
mesh-admin merged 3 commits from fix/457-a-build-waits-out-a-registry-pause into main 2026-10-11 09:17:09 +00:00
Contributor

Fixes novox/hq issue 457 (a build during the registry's nightly clean-up fails its rollout instead of waiting the two minutes out).

Acceptance: a build that meets the registry held still by the store's nightly collection waits, says so in its log, and goes on; a registry refusing longer than five minutes still fails the build, saying how long it was refused; plans retry asks every failed build of the plan's tier in one go.

1. The build waits for the registry (internal/builder)

Design chosen: the build machine waits, not a hold signalled by the collection. It is local to the one place that talks to the registry, needs no new message between modules, and also covers any other short outage (a registry restarted by its update). A refusal is the only error waited for: nothing was sent, so trying again does nothing twice.

  • New internal/builder/registry_wait.go: waitForRegistry retries on connection refused with a pause of 1 s doubling to 10 s, for up to 5 minutes (the collection held the registry 79 s on 2026-10-11). The build's log says it waits for the registry, why, and when the registry answers again; past the bound the build fails with "the registry at X refused every connection for 5m0s ... so it is down, not paused: ... connection refused".
  • Registry.client() wraps its transport so every HTTP request to the registry's own address waits (HEAD, upload, PUT, the holder manifest, mirror copies); requests to upstream registries do not. A body is re-sent through GetBody only.
  • PublishImage's docker push waits the same way.
  • Files: registry.go, registry_wait.go, registry_wait_test.go. Not check.go or failures.go (open PR #222).

2. A retry asks every failed build of the tier (cmd/mesh-controller)

Cause: a plan fails on the first failure in its tier; an outcome arriving after that finds no open plan (planBuilt reads open plans only) and is kept only in the build records. The retry read failures from the plan alone, so it asked gitea; once the plan was building again, the records failed it on plex.

Fix: retryPlan settles the tier from the build records (settleFromRecords, through recordsOfAsked, extracted from advanceOnce unchanged) before it judges and asks, so every failed build is asked; a build still running stays asked, and one recorded built is taken as built.

Tests (each failed on main for the reason in the issue)

  • TestABuildWaitsForARegistryHeldStillAndGoesOn: on main it failed with "cannot reach the registry at ...: connect: connection refused", the message seen tonight.
  • TestABuildFailsLoudlyOnARegistryRefusingPastTheBound, TestAnImagePushWaitsForARegistryHeldStill.
  • TestARetryAsksEveryFailedBuildOfTheTier: on main the retry asked [gitea]. TestARetryLeavesABuildThatRunsOrWorked.

go vet ./... is clean; go test ./internal/builder ./cmd/mesh-controller passes. The store-backed tests were not run here because this machine has no test database.

Fixes novox/hq issue 457 (a build during the registry's nightly clean-up fails its rollout instead of waiting the two minutes out). Acceptance: a build that meets the registry held still by the store's nightly collection waits, says so in its log, and goes on; a registry refusing longer than five minutes still fails the build, saying how long it was refused; `plans retry` asks every failed build of the plan's tier in one go. ## 1. The build waits for the registry (internal/builder) Design chosen: the build machine waits, not a hold signalled by the collection. It is local to the one place that talks to the registry, needs no new message between modules, and also covers any other short outage (a registry restarted by its update). A refusal is the only error waited for: nothing was sent, so trying again does nothing twice. - New `internal/builder/registry_wait.go`: `waitForRegistry` retries on connection refused with a pause of 1 s doubling to 10 s, for up to 5 minutes (the collection held the registry 79 s on 2026-10-11). The build's log says it waits for the registry, why, and when the registry answers again; past the bound the build fails with "the registry at X refused every connection for 5m0s ... so it is down, not paused: ... connection refused". - `Registry.client()` wraps its transport so every HTTP request to the registry's own address waits (HEAD, upload, PUT, the holder manifest, mirror copies); requests to upstream registries do not. A body is re-sent through `GetBody` only. - `PublishImage`'s `docker push` waits the same way. - Files: `registry.go`, `registry_wait.go`, `registry_wait_test.go`. Not `check.go` or `failures.go` (open PR #222). ## 2. A retry asks every failed build of the tier (cmd/mesh-controller) Cause: a plan fails on the first failure in its tier; an outcome arriving after that finds no open plan (`planBuilt` reads open plans only) and is kept only in the build records. The retry read failures from the plan alone, so it asked gitea; once the plan was building again, the records failed it on plex. Fix: `retryPlan` settles the tier from the build records (`settleFromRecords`, through `recordsOfAsked`, extracted from `advanceOnce` unchanged) before it judges and asks, so every failed build is asked; a build still running stays asked, and one recorded built is taken as built. ## Tests (each failed on main for the reason in the issue) - `TestABuildWaitsForARegistryHeldStillAndGoesOn`: on main it failed with "cannot reach the registry at ...: connect: connection refused", the message seen tonight. - `TestABuildFailsLoudlyOnARegistryRefusingPastTheBound`, `TestAnImagePushWaitsForARegistryHeldStill`. - `TestARetryAsksEveryFailedBuildOfTheTier`: on main the retry asked `[gitea]`. `TestARetryLeavesABuildThatRunsOrWorked`. `go vet ./...` is clean; `go test ./internal/builder ./cmd/mesh-controller` passes. The store-backed tests were not run here because this machine has no test database.
mesh-admin added 2 commits 2026-10-11 08:51:59 +00:00
The store's nightly collection stops the registry for about a minute and a
half; builds in that window failed on connection refused and failed their
whole plans. A refusal is now waited for with a growing pause, said in the
build's log, and still fails the build past the bound.
Ask every failed build of the tier on a retry, not only the first (issue 457)
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh/repo-check pass: its merge-check.sh passed
7758301444
An outcome arriving after its plan failed is kept only in the build records,
so a retry read from the plan alone asked one failed build and the records
then failed the plan again on the next. Settle the tier from the records first.
Author
Contributor

Delivery novox/mesh-controller@83ce19b9c014 — delivered since 2026-10-11T09:28:57Z

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

  • tier 0: mesh-controller
  • tier 1: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves

Machines

  • mesh-controller on novox: passed — healthy 3 times over 3m39s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 3m49s
  • build-agent on the rest running it: sent

Transitions

  • 2026-10-11 09:05 (new) → proposed (announced): novox/mesh-controller#225's head announced
  • 2026-10-11 09:10 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 09:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 09:18 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 09:18 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 09:28 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@83ce19b9c014` — **delivered** since 2026-10-11T09:28:57Z **Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives mesh-controller, build-agent - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - mesh-controller on novox: passed — healthy 3 times over 3m39s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m49s - build-agent on the rest running it: sent **Transitions** - 2026-10-11 09:05 (new) → proposed (announced): novox/mesh-controller#225's head announced - 2026-10-11 09:10 proposed → checked (checked): the verdict names this commit - 2026-10-11 09:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 09:18 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 09:18 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 09:28 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 09:05:33 +00:00
Say a registry came back only when the call worked, and retry from toRetry's set (issue 457 review)
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
83ce19b9c0
The streaming blob PUT is left unwaited, with why, since its body cannot be
read twice and the POST before it already waited.
Author
Contributor

Merge check at 77583014

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

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

  • tier 0: mesh-controller
  • tier 1: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves

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

--- the gate: build-agent, 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-11T08:51:50Z 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-11T08:51:50Z

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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-controller/cmd/mesh-builder	1.045s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	262.292s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.019s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.024s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.018s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.127s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.053s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	2.828s
ok  	github.com/novox/mesh-controller/internal/builder	3.928s
ok  	github.com/novox/mesh-controller/internal/catalogue	8.093s
ok  	github.com/novox/mesh-controller/internal/conditions	2.459s
ok  	github.com/novox/mesh-controller/internal/envfile	1.009s
ok  	github.com/novox/mesh-controller/internal/facts	1.013s
ok  	github.com/novox/mesh-controller/internal/identity	5.380s
ok  	github.com/novox/mesh-controller/internal/inventory	103.245s
ok  	github.com/novox/mesh-controller/internal/lease	17.788s
ok  	github.com/novox/mesh-controller/internal/licences	4.929s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.007s
ok  	github.com/novox/mesh-controller/internal/link	62.750s
ok  	github.com/novox/mesh-controller/internal/lint	2.321s
ok  	github.com/novox/mesh-controller/internal/outward	1.040s
ok  	github.com/novox/mesh-controller/internal/overlay	1.026s
ok  	github.com/novox/mesh-controller/internal/secrets	1.523s
ok  	github.com/novox/mesh-controller/internal/store	3.504s
ok  	github.com/novox/mesh-controller/internal/testbus	1.197s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
**Merge check** at `77583014` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives mesh-controller, build-agent - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on novox as `build-1791708729739808979` (`builds --log build-1791708729739808979`). ``` --- the gate: build-agent, 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-11T08:51:50Z 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-11T08:51:50Z 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 2 module(s) in 2 tier(s): build-agent, mesh-controller --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-controller/cmd/mesh-builder 1.045s ok github.com/novox/mesh-controller/cmd/mesh-controller 262.292s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.019s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.024s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s ok github.com/novox/mesh-controller/examples/route-proxy 1.127s ok github.com/novox/mesh-controller/internal/artifacts 1.053s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 2.828s ok github.com/novox/mesh-controller/internal/builder 3.928s ok github.com/novox/mesh-controller/internal/catalogue 8.093s ok github.com/novox/mesh-controller/internal/conditions 2.459s ok github.com/novox/mesh-controller/internal/envfile 1.009s ok github.com/novox/mesh-controller/internal/facts 1.013s ok github.com/novox/mesh-controller/internal/identity 5.380s ok github.com/novox/mesh-controller/internal/inventory 103.245s ok github.com/novox/mesh-controller/internal/lease 17.788s ok github.com/novox/mesh-controller/internal/licences 4.929s ok github.com/novox/mesh-controller/internal/licences/adapters 1.007s ok github.com/novox/mesh-controller/internal/link 62.750s ok github.com/novox/mesh-controller/internal/lint 2.321s ok github.com/novox/mesh-controller/internal/outward 1.040s ok github.com/novox/mesh-controller/internal/overlay 1.026s ok github.com/novox/mesh-controller/internal/secrets 1.523s ok github.com/novox/mesh-controller/internal/store 3.504s ok github.com/novox/mesh-controller/internal/testbus 1.197s ok github.com/novox/mesh-controller/internal/token 1.015s ```
Author
Contributor

Merge check at 83ce19b9

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

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

  • tier 0: mesh-controller
  • tier 1: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • read by no module's build: cmd/mesh-controller/plan_retry_tier_test.go, internal/builder/registry_wait_test.go

Run by the build seat on ace as build-1791709549440107278 (builds --log build-1791709549440107278).

--- the gate: build-agent, 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-11T09:00:50Z 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-11T09:00:50Z

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 2 module(s) in 2 tier(s): build-agent, mesh-controller

notes:
  - cmd/mesh-controller/plan_retry_tier_test.go and internal/builder/registry_wait_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.041s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	204.718s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.012s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.089s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.075s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.186s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.108s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	2.588s
ok  	github.com/novox/mesh-controller/internal/builder	3.527s
ok  	github.com/novox/mesh-controller/internal/catalogue	6.564s
ok  	github.com/novox/mesh-controller/internal/conditions	2.510s
ok  	github.com/novox/mesh-controller/internal/envfile	1.078s
ok  	github.com/novox/mesh-controller/internal/facts	1.080s
ok  	github.com/novox/mesh-controller/internal/identity	4.189s
ok  	github.com/novox/mesh-controller/internal/inventory	76.444s
ok  	github.com/novox/mesh-controller/internal/lease	17.717s
ok  	github.com/novox/mesh-controller/internal/licences	3.825s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.076s
ok  	github.com/novox/mesh-controller/internal/link	58.604s
ok  	github.com/novox/mesh-controller/internal/lint	2.165s
ok  	github.com/novox/mesh-controller/internal/outward	1.127s
ok  	github.com/novox/mesh-controller/internal/overlay	1.098s
ok  	github.com/novox/mesh-controller/internal/secrets	1.479s
ok  	github.com/novox/mesh-controller/internal/store	3.394s
ok  	github.com/novox/mesh-controller/internal/testbus	1.252s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
**Merge check** at `83ce19b9` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives mesh-controller, build-agent - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - read by no module's build: cmd/mesh-controller/plan_retry_tier_test.go, internal/builder/registry_wait_test.go Run by the build seat on ace as `build-1791709549440107278` (`builds --log build-1791709549440107278`). ``` --- the gate: build-agent, 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-11T09:00:50Z 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-11T09:00:50Z 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 2 module(s) in 2 tier(s): build-agent, mesh-controller notes: - cmd/mesh-controller/plan_retry_tier_test.go and internal/builder/registry_wait_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.041s ok github.com/novox/mesh-controller/cmd/mesh-controller 204.718s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.012s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.089s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.075s ok github.com/novox/mesh-controller/examples/route-proxy 1.186s ok github.com/novox/mesh-controller/internal/artifacts 1.108s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 2.588s ok github.com/novox/mesh-controller/internal/builder 3.527s ok github.com/novox/mesh-controller/internal/catalogue 6.564s ok github.com/novox/mesh-controller/internal/conditions 2.510s ok github.com/novox/mesh-controller/internal/envfile 1.078s ok github.com/novox/mesh-controller/internal/facts 1.080s ok github.com/novox/mesh-controller/internal/identity 4.189s ok github.com/novox/mesh-controller/internal/inventory 76.444s ok github.com/novox/mesh-controller/internal/lease 17.717s ok github.com/novox/mesh-controller/internal/licences 3.825s ok github.com/novox/mesh-controller/internal/licences/adapters 1.076s ok github.com/novox/mesh-controller/internal/link 58.604s ok github.com/novox/mesh-controller/internal/lint 2.165s ok github.com/novox/mesh-controller/internal/outward 1.127s ok github.com/novox/mesh-controller/internal/overlay 1.098s ok github.com/novox/mesh-controller/internal/secrets 1.479s ok github.com/novox/mesh-controller/internal/store 3.394s ok github.com/novox/mesh-controller/internal/testbus 1.252s ok github.com/novox/mesh-controller/internal/token 1.015s ```
mesh-admin merged commit 02c61b983c into main 2026-10-11 09:17:09 +00:00
mesh-admin deleted branch fix/457-a-build-waits-out-a-registry-pause 2026-10-11 09:17:09 +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#225