build-agent: declare busy, so a replaced agent finishes the check it runs (issue 594, hq ADR 0335) #260

Closed
mesh-admin wants to merge 0 commits from feat/335-a-busy-container-is-replaced-when-idle into main
Contributor

after: novox/mesh-controller

Issue 594; decision: novox/hq ADR 0335 §5. build-agent's server declares busy as mesh-builder busy (timeout: the default 10s), and its README says what that does.

Merge only after mesh-controller#283 has rolled out (and mesh-host#98 before it): a controller older than #283 copies an unknown resource key into every machine's declaration, and a node-engine older than #98 refuses the whole declaration for it. #283 sends busy only to an engine whose health statement says contract 8.

Checked: merge-check.sh with MESH_GATE set to a controller built from mesh-controller#283's head: module check, words, agent-home, paths, and the health-undeclared count (67, as kept) all pass. Against today's controller the manifest is accepted but not composed safely, which is why this waits.

after: novox/mesh-controller Issue 594; decision: novox/hq ADR 0335 §5. build-agent's `server` declares `busy` as `mesh-builder busy` (timeout: the default 10s), and its README says what that does. **Merge only after mesh-controller#283 has rolled out** (and mesh-host#98 before it): a controller older than #283 copies an unknown resource key into every machine's declaration, and a node-engine older than #98 refuses the whole declaration for it. #283 sends `busy` only to an engine whose health statement says contract 8. Checked: merge-check.sh with MESH_GATE set to a controller built from mesh-controller#283's head: module check, words, agent-home, paths, and the health-undeclared count (67, as kept) all pass. Against today's controller the manifest is accepted but not composed safely, which is why this waits.
mesh-admin added 1 commit 2026-10-12 22:54:45 +00:00
build-agent: declare busy, so a replaced agent finishes the check it runs
mesh/delivery-group group feat/335-a-busy-container-is-replaced-when-idle rejected: its order contradicts itself: novox/mesh-catalog@190608193764, novox/mesh-c…
mesh/merge-gate out of date: judged against trunk 8f80cd471634, the trunk is now 39e7a06e6293; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk 8f80cd471634, the trunk is now 39e7a06e6293; judged again on a recheck or when it is merged
mesh/delivery stopped: the pull request closed unmerged
1906081937
Every merge into mesh-controller replaced the agents and the queue started
their checks again elsewhere (issue 594). Its server now declares busy as
mesh-builder busy (novox/hq ADR 0335 §5).
Author
Contributor

Delivery novox/mesh-catalog@190608193764 — stopped since 2026-10-13T22:08:14Z

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

  • tier 0: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives build-agent
  • shanks: receives build-agent
  • build-agent 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 build-agent is judged on its first machine

Group feat/335-a-busy-container-is-replaced-when-idle, in order: novox/mesh-host@b9a293f8c8 → novox/mesh-controller@b0753e2aac

Transitions

  • 2026-10-12 22:55 (new) → proposed (announced): novox/mesh-catalog#260's head announced
  • 2026-10-12 22:58 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-12 22:58 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-13 22:08 rejected → stopped (closed): the pull request closed unmerged

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@190608193764` — **stopped** since 2026-10-13T22:08:14Z **Delivery plan** — builds build-agent → ace, g14, novox, shanks; no bus step - tier 0: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives build-agent - shanks: receives build-agent - build-agent 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 build-agent is judged on its first machine **Group** `feat/335-a-busy-container-is-replaced-when-idle`, in order: novox/mesh-host@b9a293f8c8bc → novox/mesh-controller@b0753e2aac95 - novox/mesh-host@b9a293f8c8bc before novox/mesh-controller@b0753e2aac95: declared, over built by **Transitions** - 2026-10-12 22:55 (new) → proposed (announced): novox/mesh-catalog#260's head announced - 2026-10-12 22:58 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-12 22:58 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-13 22:08 rejected → stopped (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at 19060819
Judged: head 190608193764 merged into trunk 8f80cd471634; read beside it: mesh-controller 56d6313262e8, mesh-controller-main cbac703e817d, mesh-host 7a41e120635b, mesh-tools 954e1a53eef9

  • mesh/merge-gate: FAIL — 4 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored (modules: build-agent)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

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

  • tier 0: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives build-agent
  • shanks: receives build-agent
  • build-agent 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 build-agent is judged on its first machine
  • read by no module's build: modules/build-agent/README.md

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

--- the gate: build-agent
build-agent: ok, keeps workspace (cache), ready: server by exec every 10s
long-running resources without health: 0
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T22:43:48Z 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: FAIL — 4 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored
judged by controller development build against the facts of 2026-10-12T22:43:48Z

fails:
  - a machine (f35): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored
  - a machine (yvbpsm): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored
  - 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): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored
  - holds mesh-dns-resolver (idt): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored

modules the change moves:
  - build-agent (changed)

machines:
  - a machine (f35): does not compose
  - holds mesh-dns-resolver (idt): does not compose
  - 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): does not compose
  - a machine (yvbpsm): does not compose

a merge would rebuild 1 module(s) in 1 tier(s): build-agent

notes:
  - modules/build-agent/README.md read by no module's build, and rebuild nothing (issue 280)
mesh-controller: the change fails the merge gate
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.005s
words: 12 retired words and 70 daemons' lines, none in the 45130 strings of 705 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 67, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.290s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `19060819` Judged: head `190608193764` merged into trunk `8f80cd471634`; read beside it: mesh-controller `56d6313262e8`, mesh-controller-main `cbac703e817d`, mesh-host `7a41e120635b`, mesh-tools `954e1a53eef9` - `mesh/merge-gate`: **FAIL** — 4 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored (modules: build-agent) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds build-agent → ace, g14, novox, shanks; no bus step - tier 0: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives build-agent - shanks: receives build-agent - build-agent 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 build-agent is judged on its first machine - read by no module's build: modules/build-agent/README.md Run by the build seat on shanks as `build-1791845718244784391` (`builds --log build-1791845718244784391`). ``` --- the gate: build-agent build-agent: ok, keeps workspace (cache), ready: server by exec every 10s long-running resources without health: 0 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T22:43:48Z 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: FAIL — 4 problem(s) the change brings; the first: a machine (f35): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored judged by controller development build against the facts of 2026-10-12T22:43:48Z fails: - a machine (f35): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored - a machine (yvbpsm): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored - 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): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored - holds mesh-dns-resolver (idt): nothing could be sent to it with this change — resource "build-agent.server": a container does not use "busy", and it is set. Refused rather than ignored modules the change moves: - build-agent (changed) machines: - a machine (f35): does not compose - holds mesh-dns-resolver (idt): does not compose - 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): does not compose - a machine (yvbpsm): does not compose a merge would rebuild 1 module(s) in 1 tier(s): build-agent notes: - modules/build-agent/README.md read by no module's build, and rebuild nothing (issue 280) mesh-controller: the change fails the merge gate --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.005s words: 12 retired words and 70 daemons' lines, none in the 45130 strings of 705 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 67, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.290s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin closed this pull request 2026-10-13 22:07:47 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#260