Issue 339 follow-ups: a directory used as found is said and can be handed over; the runtime's data and any .ssh refused #64

Merged
mesh-admin merged 2 commits from fix/339-found-directories-are-said into main 2026-10-09 00:15:17 +00:00
Contributor

The review's follow-ups to hq issue 339. Do not merge without review. Stacked on #63: this branch starts at #63's head (f39dbdb) because it extends #63's guard, so until #63 merges the diff here shows #63's two commits as well. Merge #63 first. The follow-up itself is the one commit 07164e4.

A directory used as found is loud:

  • every apply logs WARNING <id> (<path>): found here before the mesh and used as found: its owner <uid:gid> and mode <m> are left, though <declared> were declared …; mesh-host hand-over <path> at the machine hands it to the mesh. The record keeps what was declared (declared).
  • On every look and in every report's health statement, each such directory is its module's resource of kind directory (new link.KindDirectory), state unhealthy, reason starting used as found: and naming the owner, mode and what was declared; the path is the target (evidence). The controller's existing module-health path raises it as the module's condition after two statements (no controller change needed). Side effect, intended: an unhealthy resource holds a walk's gate for that module, so a delivery waits until someone hands the directory over.
  • mesh-host hand-over <dir> (as root, at the machine) records the directory in handed-over.json beside the state. That is its own file, so a running apply's state save cannot lose it. It refuses a path that is not a directory used as found. The next apply treats the directory as the mesh's and gives it the declared owner and mode; the guard still applies.

The guard (same paths as the controller): /var/spool, /opt, /var/lib/docker, /var/lib/containers and the runtime's configured data-root (read from /etc/docker/daemon.json) are refused for directories, accesses and mounts. An account's .ssh is refused as an access or a mount, and as a directory anywhere but below its own account's home, owned by that account. ssh-client's directories still pass.

Fail first: run on #63's head, TestTheRuntimesDataAndAnySSHAreRefused failed for every new path and kind, and .ssh outside a home was taken. The as-found and hand-over tests use new symbols, so they cannot compile there.

Live check: the guard was rerun (throwaway test, not committed) over today's plan declarations for all four nodes, with a passwd that names each node's operator account. Nothing was refused.

merge-check.sh passes locally.

The review's follow-ups to hq issue 339. Do not merge without review. **Stacked on #63**: this branch starts at #63's head (f39dbdb) because it extends #63's guard, so until #63 merges the diff here shows #63's two commits as well. Merge #63 first. The follow-up itself is the one commit 07164e4. **A directory used as found is loud:** - every apply logs `WARNING <id> (<path>): found here before the mesh and used as found: its owner <uid:gid> and mode <m> are left, though <declared> were declared …; mesh-host hand-over <path> at the machine hands it to the mesh`. The record keeps what was declared (`declared`). - On every look and in every report's health statement, each such directory is its module's resource of kind `directory` (new `link.KindDirectory`), state `unhealthy`, reason starting `used as found:` and naming the owner, mode and what was declared; the path is the target (evidence). The controller's existing module-health path raises it as the module's condition after two statements (no controller change needed). **Side effect, intended:** an unhealthy resource holds a walk's gate for that module, so a delivery waits until someone hands the directory over. - `mesh-host hand-over <dir>` (as root, at the machine) records the directory in `handed-over.json` beside the state. That is its own file, so a running apply's state save cannot lose it. It refuses a path that is not a directory used as found. The next apply treats the directory as the mesh's and gives it the declared owner and mode; the guard still applies. **The guard (same paths as the controller):** `/var/spool`, `/opt`, `/var/lib/docker`, `/var/lib/containers` and the runtime's configured `data-root` (read from `/etc/docker/daemon.json`) are refused for directories, accesses and mounts. An account's `.ssh` is refused as an access or a mount, and as a directory anywhere but below its own account's home, owned by that account. `ssh-client`'s directories still pass. **Fail first:** run on #63's head, `TestTheRuntimesDataAndAnySSHAreRefused` failed for every new path and kind, and `.ssh` outside a home was taken. The as-found and hand-over tests use new symbols, so they cannot compile there. **Live check:** the guard was rerun (throwaway test, not committed) over today's `plan` declarations for all four nodes, with a passwd that names each node's operator account. Nothing was refused. `merge-check.sh` passes locally.
mesh-admin added 3 commits 2026-10-08 22:29:15 +00:00
Refuse a placement or mount at the machine's own trees, and use a found directory as found
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check fail: its merge-check.sh failed: --- FAIL: TestBelowAHomeOnlyThatAccountsDirectoryIsPlaced (0.00s)
3a002f6e7b
A module's places setting could point a directory anywhere, with an owner it
named, and the engine chowned and chmodded whatever it was pointed at as root,
through a link too; its accesses setting could mount any path into a container
(hq issue 339). The engine now refuses, as a failed resource with its reason,
a directory, access or mount source that is or holds one of the machine's
roots, anything placed in the kernel's, the boot loader's, root's or the
engine's own trees, a non-root directory below /etc, /usr or /run, an access
there, another account's directory below a home, and a container mounting
anything it refused, judged with every link resolved. A directory whose last
component is a link is refused, and one found here that the mesh did not make
keeps its owner and mode and is never removed.
Give the home test's account a uid of its own, so it holds when the suite runs as root
mesh/delivery delivered
mesh/merge-gate pass: builds mesh-host → 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
f39dbdbaf0
Say every directory used as found, let a person hand it over, and refuse the runtime's data and any .ssh
mesh/merge-gate pass: builds mesh-host → 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
mesh/delivery superseded: a newer head of the same pull request
07164e40f3
A directory the engine used as found kept its owner and mode in silence, so
a module that cannot write it would just fail (hq issue 339 review). Each
one is now a WARNING in every apply's log and its module's resource of kind
directory, stated unhealthy on every look with its owner and what was
declared, which the controller raises as the module's condition; `mesh-host
hand-over <dir>` at the machine hands it to the mesh, and the next apply
gives it the declared owner and mode. The guard also refuses the spool, /opt,
the container runtimes' data (its configured data-root too), and an account's
.ssh as an access, a mount, or a directory anywhere but its own home.
Author
Contributor

Delivery novox/mesh-host@ae1293e73e71 — covered since 2026-10-09T07:31:59Z

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

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

Transitions

  • 2026-10-08 22:55 (new) → proposed (announced): novox/mesh-host#64's head announced
  • 2026-10-08 22:58 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 22:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 00:25 ready → held (hold): something holds it for a person: its group's composed check did not pass for the heads that merged, or it merged and no walk was opened for it
  • 2026-10-09 07:31 held → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-host@7c046a8a1d (merged as d28ca959 into main, walk plan-1791504934730503217): mesh-host

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-host@ae1293e73e71` — **covered** since 2026-10-09T07:31:59Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Transitions** - 2026-10-08 22:55 (new) → proposed (announced): novox/mesh-host#64's head announced - 2026-10-08 22:58 proposed → checked (checked): the verdict names this commit - 2026-10-08 22:58 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 00:25 ready → held (hold): something holds it for a person: its group's composed check did not pass for the heads that merged, or it merged and no walk was opened for it - 2026-10-09 07:31 held → covered (covered): covered: a later merge that contains it was delivered: novox/mesh-host@7c046a8a1d84 (merged as d28ca959 into main, walk plan-1791504934730503217): mesh-host The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at 07164e40

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

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

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

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

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T22:31:56Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-08T22:31:56Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.014s
ok  	github.com/novox/mesh-host/cmd/mesh-host	5.423s
ok  	github.com/novox/mesh-host/examples	1.019s
ok  	github.com/novox/mesh-host/internal/accounts	1.045s
ok  	github.com/novox/mesh-host/internal/apply	4.676s
ok  	github.com/novox/mesh-host/internal/bootstrap	1.679s
ok  	github.com/novox/mesh-host/internal/bundle	1.046s
ok  	github.com/novox/mesh-host/internal/declaration	1.091s
ok  	github.com/novox/mesh-host/internal/firewall	1.870s
ok  	github.com/novox/mesh-host/internal/identity	1.188s
ok  	github.com/novox/mesh-host/internal/image	1.046s
ok  	github.com/novox/mesh-host/internal/inventory	1.050s
ok  	github.com/novox/mesh-host/internal/link	10.375s
ok  	github.com/novox/mesh-host/internal/liveness	2.148s
ok  	github.com/novox/mesh-host/internal/network	1.107s
ok  	github.com/novox/mesh-host/internal/outward	1.058s
ok  	github.com/novox/mesh-host/internal/profile	1.539s
ok  	github.com/novox/mesh-host/internal/reachable	1.054s
ok  	github.com/novox/mesh-host/internal/store	1.289s
ok  	github.com/novox/mesh-host/internal/system	1.054s
ok  	github.com/novox/mesh-host/internal/tunnel	1.054s
ok  	github.com/novox/mesh-host/internal/units	1.038s
ok  	github.com/novox/mesh-host/internal/upgrade	1.227s
ok  	github.com/novox/mesh-host/internal/witness	4.872s
ok  	github.com/novox/mesh-host/packaging	1.051s
ok  	github.com/novox/mesh-host/validate	1.049s
**Merge check** at `07164e40` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host Run by the build seat on shanks as `build-1791499008569562177` (`builds --log build-1791499008569562177`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T22:31:56Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-08T22:31:56Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-host --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s ok github.com/novox/mesh-host/cmd/mesh-host 5.423s ok github.com/novox/mesh-host/examples 1.019s ok github.com/novox/mesh-host/internal/accounts 1.045s ok github.com/novox/mesh-host/internal/apply 4.676s ok github.com/novox/mesh-host/internal/bootstrap 1.679s ok github.com/novox/mesh-host/internal/bundle 1.046s ok github.com/novox/mesh-host/internal/declaration 1.091s ok github.com/novox/mesh-host/internal/firewall 1.870s ok github.com/novox/mesh-host/internal/identity 1.188s ok github.com/novox/mesh-host/internal/image 1.046s ok github.com/novox/mesh-host/internal/inventory 1.050s ok github.com/novox/mesh-host/internal/link 10.375s ok github.com/novox/mesh-host/internal/liveness 2.148s ok github.com/novox/mesh-host/internal/network 1.107s ok github.com/novox/mesh-host/internal/outward 1.058s ok github.com/novox/mesh-host/internal/profile 1.539s ok github.com/novox/mesh-host/internal/reachable 1.054s ok github.com/novox/mesh-host/internal/store 1.289s ok github.com/novox/mesh-host/internal/system 1.054s ok github.com/novox/mesh-host/internal/tunnel 1.054s ok github.com/novox/mesh-host/internal/units 1.038s ok github.com/novox/mesh-host/internal/upgrade 1.227s ok github.com/novox/mesh-host/internal/witness 4.872s ok github.com/novox/mesh-host/packaging 1.051s ok github.com/novox/mesh-host/validate 1.049s ```
jschoubben added 1 commit 2026-10-08 22:55:24 +00:00
Read every runtime's data root, keep when a directory was found, and key a hand-over to its resource
mesh/merge-gate pass: builds mesh-host → 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
mesh/delivery covered: a later merge that contains it was delivered: novox/mesh-host@7c046a8a1d84 (merged as d28ca959 into main, walk plan-17915049347305…
ae1293e73e
The review of #64 asked for containerd's tree, dockerd's --data-root from its
unit and drop-ins, and podman's graphroot to be refused like docker's own
(hq issue 339); and the controller now tells a directory a send found from
one found before it, which needs the time it was first found kept across
applies instead of the time of the last apply. A hand-over now names the
resource it was for, so it lapses if another declaration points at the path.
Author
Contributor

Merge check at ae1293e7

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

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

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host

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

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T22:54: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: 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-08T22:54:48Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.018s
ok  	github.com/novox/mesh-host/cmd/mesh-host	7.510s
ok  	github.com/novox/mesh-host/examples	1.024s
ok  	github.com/novox/mesh-host/internal/accounts	1.421s
ok  	github.com/novox/mesh-host/internal/apply	24.656s
ok  	github.com/novox/mesh-host/internal/bootstrap	2.771s
ok  	github.com/novox/mesh-host/internal/bundle	1.019s
ok  	github.com/novox/mesh-host/internal/declaration	1.066s
ok  	github.com/novox/mesh-host/internal/firewall	1.859s
ok  	github.com/novox/mesh-host/internal/identity	1.679s
ok  	github.com/novox/mesh-host/internal/image	1.021s
ok  	github.com/novox/mesh-host/internal/inventory	1.022s
ok  	github.com/novox/mesh-host/internal/link	10.345s
ok  	github.com/novox/mesh-host/internal/liveness	2.474s
ok  	github.com/novox/mesh-host/internal/network	1.141s
ok  	github.com/novox/mesh-host/internal/outward	1.018s
ok  	github.com/novox/mesh-host/internal/profile	1.488s
ok  	github.com/novox/mesh-host/internal/reachable	1.016s
ok  	github.com/novox/mesh-host/internal/store	1.887s
ok  	github.com/novox/mesh-host/internal/system	1.017s
ok  	github.com/novox/mesh-host/internal/tunnel	1.018s
ok  	github.com/novox/mesh-host/internal/units	1.009s
ok  	github.com/novox/mesh-host/internal/upgrade	1.670s
ok  	github.com/novox/mesh-host/internal/witness	31.574s
ok  	github.com/novox/mesh-host/packaging	1.015s
ok  	github.com/novox/mesh-host/validate	1.012s
**Merge check** at `ae1293e7` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host Run by the build seat on novox as `build-1791500126339865576` (`builds --log build-1791500126339865576`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T22:54: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: 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-08T22:54:48Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-host --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.018s ok github.com/novox/mesh-host/cmd/mesh-host 7.510s ok github.com/novox/mesh-host/examples 1.024s ok github.com/novox/mesh-host/internal/accounts 1.421s ok github.com/novox/mesh-host/internal/apply 24.656s ok github.com/novox/mesh-host/internal/bootstrap 2.771s ok github.com/novox/mesh-host/internal/bundle 1.019s ok github.com/novox/mesh-host/internal/declaration 1.066s ok github.com/novox/mesh-host/internal/firewall 1.859s ok github.com/novox/mesh-host/internal/identity 1.679s ok github.com/novox/mesh-host/internal/image 1.021s ok github.com/novox/mesh-host/internal/inventory 1.022s ok github.com/novox/mesh-host/internal/link 10.345s ok github.com/novox/mesh-host/internal/liveness 2.474s ok github.com/novox/mesh-host/internal/network 1.141s ok github.com/novox/mesh-host/internal/outward 1.018s ok github.com/novox/mesh-host/internal/profile 1.488s ok github.com/novox/mesh-host/internal/reachable 1.016s ok github.com/novox/mesh-host/internal/store 1.887s ok github.com/novox/mesh-host/internal/system 1.017s ok github.com/novox/mesh-host/internal/tunnel 1.018s ok github.com/novox/mesh-host/internal/units 1.009s ok github.com/novox/mesh-host/internal/upgrade 1.670s ok github.com/novox/mesh-host/internal/witness 31.574s ok github.com/novox/mesh-host/packaging 1.015s ok github.com/novox/mesh-host/validate 1.012s ```
mesh-admin merged commit b232db4e17 into main 2026-10-09 00:15:17 +00:00
mesh-admin deleted branch fix/339-found-directories-are-said 2026-10-09 00:15:17 +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-host#64