restic: a failed backup, a failed thinning and a refused retention raise a condition (hq issue 454) #210

Merged
mesh-admin merged 2 commits from fix/454-a-failed-backup-is-raised into main 2026-10-11 10:18:25 +00:00
Contributor

Fixes novox/hq issue 454: the restic module raised no condition when a backup failed or its retention was refused.

Acceptance: a night that leaves a module without a backup, a thinning that fails, or a retention file that is missing or unreadable makes restic unhealthy on that machine, and the controller raises module.restic.<machine>.unhealthy with words naming what failed and what to do. A refused retention setting raises module.restic.<machine>.needs-operator, naming the setting.

What changes

  • The night and the measuring are processes (restic-night, restic-measure), run as ${machine:account} like the tool runtime, with the bundle's env. A module raises a condition only through the health of something it runs (ADR 0240, ADR 0256), and a tool check needs a check of another kind beside it (ADR 0240 rule 2). So the night is judged by the new tool backup_health, and the measuring by its unit. The tool runtime now serves only the verbs and the health tool.

  • backup_health answers:

    • unhealthy when a module declared here was NOT backed up at its last night (it names the module, the error, its newest restore point, and node-backup.now {"module": ...});
    • unhealthy when the night did not run at all, or when the last thinning failed ("every restore point is kept ... node-backup.now thins again");
    • unhealthy when the retention file is missing or unreadable (push the machine);
    • waits (ADR 0283), naming the setting, when one of keep-daily, keep-weekly or keep-monthly is refused.

    A later good backup or thinning clears it. The night records its own outcome and its thinning in run.json.

  • A file lock (night.lock, measure.lock) replaces the in-process mutexes. A night in its process and now, restore or a retired item's deletion in the tool runtime never run at the same time.

  • The retention file is read as root when the account may not read it. The mesh writes it as root:root 0600 (a trusted file). On shanks I saw -rw------- root root /var/lib/restic/retention.conf, and the tool runtime runs as the operator account. So from tonight every machine's night would have refused it as unreadable and thinned nothing. The read is cached by the file's stat, so the health check does not run sudo every minute.

  • A missing retention file is refused, no longer read as 14/8/6. Every machine has the file: each machine's plan carries restic.retention, a push would change nothing for restic on any of them, and all four report current and applied. On shanks I also checked the file on disk.

  • backed-up says, beside each module, retention (daily/weekly/monthly, or refused and setting) and thinned (the last thinning). The answer stays the list the controller's readHolder reads.

  • mesh-sdk moves to the version mounts uses, for its health package.

Not touched

Issue 453 (a hand-taken backup forgotten by the next thinning) is left alone. This change records the outcome around the forget call in BackUp, but the call's arguments (--group-by host,tags and the keep flags) are unchanged. A fix for 453 edits the same lines.

Checked

  • Tests written first. On main, TestWithoutTheFileANightThinsNothingAndSaysTheFileIsMissing and TestARetentionOnlyRootMayReadIsReadAsRoot fail on behaviour (main thinned by 14/8/6 without a file, and never read as root). The health tests do not compile on main, because Health and hold do not exist there.
  • go vet ./... and go test -race ./... -count=1 in modules/restic: ok.
  • merge-check.sh with the controller of main as MESH_GATE: words, agent-home and paths ok. module check says restic: ok, 3 tool(s) ... ready: night by its tool backup_health every 1m0s; measure by unit every 30s. Long-running resources without health stay at 69.

For the rollout

The first machine's gate judges backup_health. A module whose last night failed there fails the gate, as ADR 0240 intends. ace's last night (03:00) was good for every module.

Fixes novox/hq issue 454: the restic module raised no condition when a backup failed or its retention was refused. **Acceptance:** a night that leaves a module without a backup, a thinning that fails, or a retention file that is missing or unreadable makes `restic` unhealthy on that machine, and the controller raises `module.restic.<machine>.unhealthy` with words naming what failed and what to do. A refused retention setting raises `module.restic.<machine>.needs-operator`, naming the setting. ## What changes - **The night and the measuring are processes** (`restic-night`, `restic-measure`), run as `${machine:account}` like the tool runtime, with the bundle's env. A module raises a condition only through the health of something it runs (ADR 0240, ADR 0256), and a tool check needs a check of another kind beside it (ADR 0240 rule 2). So the night is judged by the new tool `backup_health`, and the measuring by its unit. The tool runtime now serves only the verbs and the health tool. - **`backup_health`** answers: - *unhealthy* when a module declared here was NOT backed up at its last night (it names the module, the error, its newest restore point, and `node-backup.now {"module": ...}`); - *unhealthy* when the night did not run at all, or when the last thinning failed ("every restore point is kept ... node-backup.now thins again"); - *unhealthy* when the retention file is missing or unreadable (push the machine); - *waits* (ADR 0283), naming the setting, when one of `keep-daily`, `keep-weekly` or `keep-monthly` is refused. A later good backup or thinning clears it. The night records its own outcome and its thinning in `run.json`. - **A file lock** (`night.lock`, `measure.lock`) replaces the in-process mutexes. A night in its process and `now`, `restore` or a retired item's deletion in the tool runtime never run at the same time. - **The retention file is read as root when the account may not read it.** The mesh writes it as root:root 0600 (a trusted file). On shanks I saw `-rw------- root root /var/lib/restic/retention.conf`, and the tool runtime runs as the operator account. So from tonight every machine's night would have refused it as unreadable and thinned nothing. The read is cached by the file's stat, so the health check does not run sudo every minute. - **A missing retention file is refused**, no longer read as 14/8/6. Every machine has the file: each machine's plan carries `restic.retention`, a push would change nothing for restic on any of them, and all four report current and applied. On shanks I also checked the file on disk. - **`backed-up`** says, beside each module, `retention` (`daily`/`weekly`/`monthly`, or `refused` and `setting`) and `thinned` (the last thinning). The answer stays the list the controller's `readHolder` reads. - mesh-sdk moves to the version `mounts` uses, for its `health` package. ## Not touched Issue 453 (a hand-taken backup forgotten by the next thinning) is left alone. This change records the outcome around the `forget` call in `BackUp`, but the call's arguments (`--group-by host,tags` and the keep flags) are unchanged. A fix for 453 edits the same lines. ## Checked - Tests written first. On main, `TestWithoutTheFileANightThinsNothingAndSaysTheFileIsMissing` and `TestARetentionOnlyRootMayReadIsReadAsRoot` fail on behaviour (main thinned by 14/8/6 without a file, and never read as root). The health tests do not compile on main, because `Health` and `hold` do not exist there. - `go vet ./...` and `go test -race ./... -count=1` in modules/restic: ok. - `merge-check.sh` with the controller of main as `MESH_GATE`: words, agent-home and paths ok. `module check` says `restic: ok, 3 tool(s) ... ready: night by its tool backup_health every 1m0s; measure by unit every 30s`. Long-running resources without health stay at 69. ## For the rollout The first machine's gate judges `backup_health`. A module whose last night failed there fails the gate, as ADR 0240 intends. ace's last night (03:00) was good for every module.
mesh-admin added 1 commit 2026-10-11 09:56:42 +00:00
restic: raise a failed backup, a failed thinning and a refused retention as the module's health (novox/hq issue 454)
mesh/merge-gate pass: builds restic → ace, g14, novox, shanks; 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
d649309895
A failed night was a journal line only, so a typo in a retention setting
let the repository grow until a disk filled. The night and the measuring
now run as processes the node-engine judges: the night by backup_health,
which is unhealthy for a module not backed up, a night that did not run,
a failed thinning or a missing retention file, and waits naming the
setting when one is refused; the measuring by its unit. A file lock
keeps a night and the tool runtime's now and restore apart.

The retention file is root's alone, so the account reads it through sudo:
until now every night would have refused it as unreadable. Every machine
has the file, so a missing one is refused instead of thinned by 14/8/6.
backed-up says the retention in force and the last thinning per module.
Author
Contributor

Delivery novox/mesh-catalog@cbe9fa7a2c19 — delivered since 2026-10-11T10:31:16Z

Delivery plan — builds restic → ace, g14, novox, shanks; no bus step

  • tier 0: restic
  • ace: receives restic
  • g14: receives restic
  • novox: receives restic
  • shanks: receives restic
  • restic keeps data (ADR 0233): what it holds is backed up before it moves

Machines

  • restic on ace: passed — healthy 3 times over 10m1s
  • restic on the rest running it: sent

Transitions

  • 2026-10-11 10:15 (new) → proposed (announced): novox/mesh-catalog#210's head announced
  • 2026-10-11 10:17 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 10:17 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 10:20 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 10:20 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 10:31 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-catalog@cbe9fa7a2c19` — **delivered** since 2026-10-11T10:31:16Z **Delivery plan** — builds restic → ace, g14, novox, shanks; no bus step - tier 0: restic - ace: receives restic - g14: receives restic - novox: receives restic - shanks: receives restic - restic keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - restic on ace: passed — healthy 3 times over 10m1s - restic on the rest running it: sent **Transitions** - 2026-10-11 10:15 (new) → proposed (announced): novox/mesh-catalog#210's head announced - 2026-10-11 10:17 proposed → checked (checked): the verdict names this commit - 2026-10-11 10:17 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 10:20 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 10:20 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 10:31 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`.
Author
Contributor

Merge check at d6493098

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
  • 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 restic → ace, g14, novox, shanks; no bus step

  • tier 0: restic
  • ace: receives restic
  • g14: receives restic
  • novox: receives restic
  • shanks: receives restic
  • restic keeps data (ADR 0233): what it holds is backed up before it moves
  • read by no module's build: modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go

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

--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
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-11T09:55:21Z 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:55:21Z

modules the change moves:
  - restic (changed)

machines:
  - a machine (f35): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)
  - holds mesh-dns-resolver (idt): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)
  - 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; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)
  - a machine (yvbpsm): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)

a merge would rebuild 1 module(s) in 1 tier(s): restic

notes:
  - modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.006s
words: 12 retired words and 70 daemons' lines, none in the 41468 strings of 673 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.014s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.008s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/restic
ok  	restic/cmd/restic-backups	1.328s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `d6493098` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: restic) - `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 restic → ace, g14, novox, shanks; no bus step - tier 0: restic - ace: receives restic - g14: receives restic - novox: receives restic - shanks: receives restic - restic keeps data (ADR 0233): what it holds is backed up before it moves - read by no module's build: modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go Run by the build seat on novox as `build-1791712614851166957` (`builds --log build-1791712614851166957`). ``` --- the gate: restic restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s 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-11T09:55:21Z 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:55:21Z modules the change moves: - restic (changed) machines: - a machine (f35): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) - holds mesh-dns-resolver (idt): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) - 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; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) - a machine (yvbpsm): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) a merge would rebuild 1 module(s) in 1 tier(s): restic notes: - modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.006s words: 12 retired words and 70 daemons' lines, none in the 41468 strings of 673 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.014s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.008s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 69, as kept testing modules/restic ok restic/cmd/restic-backups 1.328s --- its merge-check-typescript.sh (typescript toolchain) ```
jschoubben added 1 commit 2026-10-11 10:14:56 +00:00
restic: raise a night that never happens, and have the mesh write the retention readable (novox/hq issue 454)
mesh/merge-gate pass: builds restic → ace, g14, novox, shanks; 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
cbe9fa7a2c
A hung night, a lock held for hours or a lock that cannot be taken left no
failed night behind, so it stayed healthy. The night's process now counts
how long the machine was up since its newest good night, by the monotonic
clock so a sleeping laptop is not blamed, and past 26 hours it is raised.

The retention file is written 0644 and root's instead of read through
sudo: the account reads it and still cannot change it. An unreadable file
names its cause, and the healthy answer says only what was seen.
Author
Contributor

Merge check at cbe9fa7a

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
  • 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 restic → ace, g14, novox, shanks; no bus step

  • tier 0: restic
  • ace: receives restic
  • g14: receives restic
  • novox: receives restic
  • shanks: receives restic
  • restic keeps data (ADR 0233): what it holds is backed up before it moves
  • read by no module's build: modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go

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

--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
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-11T10:05:21Z 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-11T10:05:21Z

modules the change moves:
  - restic (changed)

machines:
  - a machine (f35): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)
  - holds mesh-dns-resolver (idt): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)
  - 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; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)
  - a machine (yvbpsm): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night)

a merge would rebuild 1 module(s) in 1 tier(s): restic

notes:
  - modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 41490 strings of 674 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: 69, as kept
testing modules/restic
ok  	restic/cmd/restic-backups	1.283s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `cbe9fa7a` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: restic) - `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 restic → ace, g14, novox, shanks; no bus step - tier 0: restic - ace: receives restic - g14: receives restic - novox: receives restic - shanks: receives restic - restic keeps data (ADR 0233): what it holds is backed up before it moves - read by no module's build: modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go Run by the build seat on shanks as `build-1791713713857548096` (`builds --log build-1791713713857548096`). ``` --- the gate: restic restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s 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-11T10:05:21Z 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-11T10:05:21Z modules the change moves: - restic (changed) machines: - a machine (f35): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) - holds mesh-dns-resolver (idt): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) - 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; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) - a machine (yvbpsm): composes; the change adds 2 resource(s) and removes 0 (+process:restic.measure, +process:restic.night) a merge would rebuild 1 module(s) in 1 tier(s): restic notes: - modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 41490 strings of 674 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: 69, as kept testing modules/restic ok restic/cmd/restic-backups 1.283s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit 0557be174a into main 2026-10-11 10:18:25 +00:00
mesh-admin deleted branch fix/454-a-failed-backup-is-raised 2026-10-11 10:18:26 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#210