A shrink is read against the item's own path: a moved directory starts its size history again (hq issue 368) #204

Merged
mesh-admin merged 2 commits from fix/368-data-shrank-path-change into main 2026-10-10 15:56:13 +00:00
Contributor

Fixes novox/hq issue 368 (the data-shrank watch compares two different directories after a path change).

Symptom. On 2026-10-10 02:34 data-shrank was raised for agent-home of claude-code on the control-node: 490 B from 94.7 MB. The agent's home had moved from the operator's own home to the agent account's (hq ADR 0266); no data was lost.

Cause. data_reading (migration 0072) kept sizes by machine, module and item only, and DataPeaks took the largest of the last seven days across all of them — so the fresh new directory was read against the old one's size.

Fix.

  • Migration 0092: data_reading gets a path; every reading kept so far takes its item's path now (where it was really measured is not on record; this keeps every history, so a real shrink stays raised).
  • RecordData keeps each reading with the item's path after the measurement (the holder's, or the last known one when it named none); the once-an-hour rule is per path, so a moved item is read at once.
  • DataPeaks reads only readings at the item's path now. A moved item starts its size history again; moving back reads it against what that path held.

Tests (both fail before the fix, pass after):

  • internal/inventory TestThePeakIsReadAtTheItemsPathOnly: path move, genuine shrink at the new path, a measurement naming no path, moving back.
  • cmd/mesh-controller TestAMovedPathIsNoShrinkAndAShrinkThereStillIs: the incident replayed through the store into dataFindings — nothing raised on the move, data-shrank (urgent) raised for a genuine shrink at the new path.

merge-check.sh passes locally against postgres 17.

Not changed: the open condition on the control-node was raised before this; its old readings stay until they leave the seven-day window (about 2026-10-17 02:28), inside the operator's silence that lasts until 02:53.

Fixes novox/hq issue 368 (the data-shrank watch compares two different directories after a path change). **Symptom.** On 2026-10-10 02:34 `data-shrank` was raised for agent-home of claude-code on the control-node: 490 B from 94.7 MB. The agent's home had moved from the operator's own home to the agent account's (hq ADR 0266); no data was lost. **Cause.** `data_reading` (migration 0072) kept sizes by machine, module and item only, and `DataPeaks` took the largest of the last seven days across all of them — so the fresh new directory was read against the old one's size. **Fix.** - Migration 0092: `data_reading` gets a `path`; every reading kept so far takes its item's path now (where it was really measured is not on record; this keeps every history, so a real shrink stays raised). - `RecordData` keeps each reading with the item's path after the measurement (the holder's, or the last known one when it named none); the once-an-hour rule is per path, so a moved item is read at once. - `DataPeaks` reads only readings at the item's path now. A moved item starts its size history again; moving back reads it against what that path held. **Tests** (both fail before the fix, pass after): - `internal/inventory` `TestThePeakIsReadAtTheItemsPathOnly`: path move, genuine shrink at the new path, a measurement naming no path, moving back. - `cmd/mesh-controller` `TestAMovedPathIsNoShrinkAndAShrinkThereStillIs`: the incident replayed through the store into `dataFindings` — nothing raised on the move, `data-shrank` (urgent) raised for a genuine shrink at the new path. `merge-check.sh` passes locally against postgres 17. **Not changed:** the open condition on the control-node was raised before this; its old readings stay until they leave the seven-day window (about 2026-10-17 02:28), inside the operator's silence that lasts until 02:53.
mesh-admin added 1 commit 2026-10-10 15:42:59 +00:00
Read a shrink against the item's own path, so a moved directory starts its size history again (hq issue 368)
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 superseded: a newer head of the same pull request
96b0966ad8
A reading now keeps the path it was measured at, and the peak is read only from
readings at the item's path now. Before, an agent's home that moved to its own
account was compared with the operator's home it left, and data-shrank was
raised for data that was never lost. Existing readings take their item's path
now, so a shrink that is real stays raised.
Author
Contributor

Delivery novox/mesh-controller@babfef4f3ad8 — delivered since 2026-10-10T16:09:15Z

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 3m37s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 3m37s
  • build-agent on the rest running it: sent

Transitions

  • 2026-10-10 15:49 (new) → proposed (announced): novox/mesh-controller#204's head announced
  • 2026-10-10 15:55 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 15:55 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 15:57 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 15:57 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-10 16:09 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@babfef4f3ad8` — **delivered** since 2026-10-10T16:09:15Z **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 3m37s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m37s - build-agent on the rest running it: sent **Transitions** - 2026-10-10 15:49 (new) → proposed (announced): novox/mesh-controller#204's head announced - 2026-10-10 15:55 proposed → checked (checked): the verdict names this commit - 2026-10-10 15:55 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 15:57 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 15:57 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-10 16:09 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-10 15:48:52 +00:00
Keep one reading when two paths are measured at one moment, rather than failing the machine's record (hq issue 368 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
babfef4f3a
Author
Contributor

Merge check at 96b0966a

  • 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/data_test.go, internal/inventory/data_test.go

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

--- 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-10T15:36:57Z 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-10T15:36:57Z

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/data_test.go and internal/inventory/data_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.042s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	227.235s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.018s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.029s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.015s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.210s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.052s
ok  	github.com/novox/mesh-controller/internal/broker	3.547s
ok  	github.com/novox/mesh-controller/internal/builder	4.764s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.674s
ok  	github.com/novox/mesh-controller/internal/conditions	2.430s
ok  	github.com/novox/mesh-controller/internal/envfile	1.037s
ok  	github.com/novox/mesh-controller/internal/facts	1.045s
ok  	github.com/novox/mesh-controller/internal/identity	6.085s
ok  	github.com/novox/mesh-controller/internal/inventory	86.596s
ok  	github.com/novox/mesh-controller/internal/lease	18.826s
ok  	github.com/novox/mesh-controller/internal/licences	5.519s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.011s
ok  	github.com/novox/mesh-controller/internal/link	55.533s
ok  	github.com/novox/mesh-controller/internal/lint	1.926s
ok  	github.com/novox/mesh-controller/internal/outward	1.035s
ok  	github.com/novox/mesh-controller/internal/overlay	1.027s
ok  	github.com/novox/mesh-controller/internal/secrets	1.361s
ok  	github.com/novox/mesh-controller/internal/store	3.952s
ok  	github.com/novox/mesh-controller/internal/testbus	1.192s
ok  	github.com/novox/mesh-controller/internal/token	1.020s
**Merge check** at `96b0966a` - `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/data_test.go, internal/inventory/data_test.go Run by the build seat on g14 as `build-1791646982778771120` (`builds --log build-1791646982778771120`). ``` --- 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-10T15:36:57Z 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-10T15:36:57Z 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/data_test.go and internal/inventory/data_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.042s ok github.com/novox/mesh-controller/cmd/mesh-controller 227.235s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.018s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.029s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.015s ok github.com/novox/mesh-controller/examples/route-proxy 1.210s ok github.com/novox/mesh-controller/internal/artifacts 1.052s ok github.com/novox/mesh-controller/internal/broker 3.547s ok github.com/novox/mesh-controller/internal/builder 4.764s ok github.com/novox/mesh-controller/internal/catalogue 4.674s ok github.com/novox/mesh-controller/internal/conditions 2.430s ok github.com/novox/mesh-controller/internal/envfile 1.037s ok github.com/novox/mesh-controller/internal/facts 1.045s ok github.com/novox/mesh-controller/internal/identity 6.085s ok github.com/novox/mesh-controller/internal/inventory 86.596s ok github.com/novox/mesh-controller/internal/lease 18.826s ok github.com/novox/mesh-controller/internal/licences 5.519s ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s ok github.com/novox/mesh-controller/internal/link 55.533s ok github.com/novox/mesh-controller/internal/lint 1.926s ok github.com/novox/mesh-controller/internal/outward 1.035s ok github.com/novox/mesh-controller/internal/overlay 1.027s ok github.com/novox/mesh-controller/internal/secrets 1.361s ok github.com/novox/mesh-controller/internal/store 3.952s ok github.com/novox/mesh-controller/internal/testbus 1.192s ok github.com/novox/mesh-controller/internal/token 1.020s ```
Author
Contributor

Independent review (a separate reviewer agent), approved at head babfef4.

Checklist: glossary words PASS; failure stays loud PASS (per-item and dataset shrink read the same peaks; the backfill keeps every history); a moved path neither raises nor silences forever PASS (history restarts at the new path; empty path keeps the last known; moving back reads the old peak); tests cover the path change and a genuine shrink, and fail without the fix PASS; no secrets in events or logs PASS.

Finding taken: the reading insert could break the reading's key when two paths were measured at one moment, failing the machine's whole record; fixed in babfef4 with on conflict do nothing and TestTwoPathsAtOneMomentFailNothing. Limits recorded on hq issue 368: the novox false alarm stays until its old readings leave the 7-day window (about 2026-10-17 02:28); data lost in a move itself is not caught.

Independent review (a separate reviewer agent), approved at head babfef4. Checklist: glossary words PASS; failure stays loud PASS (per-item and dataset shrink read the same peaks; the backfill keeps every history); a moved path neither raises nor silences forever PASS (history restarts at the new path; empty path keeps the last known; moving back reads the old peak); tests cover the path change and a genuine shrink, and fail without the fix PASS; no secrets in events or logs PASS. Finding taken: the reading insert could break the reading's key when two paths were measured at one moment, failing the machine's whole record; fixed in babfef4 with `on conflict do nothing` and TestTwoPathsAtOneMomentFailNothing. Limits recorded on hq issue 368: the novox false alarm stays until its old readings leave the 7-day window (about 2026-10-17 02:28); data lost in a move itself is not caught.
Author
Contributor

Merge check at babfef4f

  • 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/data_test.go, internal/inventory/data_test.go

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

--- 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-10T15:46:57Z 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-10T15:46:57Z

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/data_test.go and internal/inventory/data_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	228.107s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.023s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.041s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.031s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.251s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.074s
ok  	github.com/novox/mesh-controller/internal/broker	2.815s
ok  	github.com/novox/mesh-controller/internal/builder	2.617s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.754s
ok  	github.com/novox/mesh-controller/internal/conditions	2.498s
ok  	github.com/novox/mesh-controller/internal/envfile	1.029s
ok  	github.com/novox/mesh-controller/internal/facts	1.047s
ok  	github.com/novox/mesh-controller/internal/identity	4.299s
ok  	github.com/novox/mesh-controller/internal/inventory	78.894s
ok  	github.com/novox/mesh-controller/internal/lease	17.755s
ok  	github.com/novox/mesh-controller/internal/licences	3.949s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.014s
ok  	github.com/novox/mesh-controller/internal/link	51.887s
ok  	github.com/novox/mesh-controller/internal/lint	2.133s
ok  	github.com/novox/mesh-controller/internal/outward	1.040s
ok  	github.com/novox/mesh-controller/internal/overlay	1.037s
ok  	github.com/novox/mesh-controller/internal/secrets	1.462s
ok  	github.com/novox/mesh-controller/internal/store	3.351s
ok  	github.com/novox/mesh-controller/internal/testbus	1.191s
ok  	github.com/novox/mesh-controller/internal/token	1.027s
**Merge check** at `babfef4f` - `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/data_test.go, internal/inventory/data_test.go Run by the build seat on g14 as `build-1791647348087054091` (`builds --log build-1791647348087054091`). ``` --- 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-10T15:46:57Z 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-10T15:46:57Z 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/data_test.go and internal/inventory/data_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 228.107s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.023s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.041s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.031s ok github.com/novox/mesh-controller/examples/route-proxy 1.251s ok github.com/novox/mesh-controller/internal/artifacts 1.074s ok github.com/novox/mesh-controller/internal/broker 2.815s ok github.com/novox/mesh-controller/internal/builder 2.617s ok github.com/novox/mesh-controller/internal/catalogue 4.754s ok github.com/novox/mesh-controller/internal/conditions 2.498s ok github.com/novox/mesh-controller/internal/envfile 1.029s ok github.com/novox/mesh-controller/internal/facts 1.047s ok github.com/novox/mesh-controller/internal/identity 4.299s ok github.com/novox/mesh-controller/internal/inventory 78.894s ok github.com/novox/mesh-controller/internal/lease 17.755s ok github.com/novox/mesh-controller/internal/licences 3.949s ok github.com/novox/mesh-controller/internal/licences/adapters 1.014s ok github.com/novox/mesh-controller/internal/link 51.887s ok github.com/novox/mesh-controller/internal/lint 2.133s ok github.com/novox/mesh-controller/internal/outward 1.040s ok github.com/novox/mesh-controller/internal/overlay 1.037s ok github.com/novox/mesh-controller/internal/secrets 1.462s ok github.com/novox/mesh-controller/internal/store 3.351s ok github.com/novox/mesh-controller/internal/testbus 1.191s ok github.com/novox/mesh-controller/internal/token 1.027s ```
mesh-admin merged commit 798738cc12 into main 2026-10-10 15:56:13 +00:00
mesh-admin deleted branch fix/368-data-shrank-path-change 2026-10-10 15:56:14 +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#204