Why (issue 522, after #225). On novox, netcheck_tunnel answered wg show mesh0: Unable to access interface: Operation not permitted: novox's tool runner runs as the operator's account, not root, and the tunnel answers only to root. #225 ran wg directly, so it worked only where the runner is root.
What changes: wg runs as given when the process is root, else through sudo -n — the pattern the nftables module uses for nft (ADR 0175 §4: root is the module's concern; the sudo module allows the runtime's account without a prompt). A sudo refusal is said as such. novox's own node-packet-filter.rules reads nftables this way today, so the rule is in place there.
Checked: merge-check.sh: netcheck ok; go vet, go test -race green; new test: the command as root and through sudo.
**Why** (issue 522, after #225). On novox, `netcheck_tunnel` answered `wg show mesh0: Unable to access interface: Operation not permitted`: novox's tool runner runs as the operator's account, not root, and the tunnel answers only to root. #225 ran `wg` directly, so it worked only where the runner is root.
**What changes**: `wg` runs as given when the process is root, else through `sudo -n` — the pattern the nftables module uses for `nft` (ADR 0175 §4: root is the module's concern; the sudo module allows the runtime's account without a prompt). A sudo refusal is said as such. novox's own `node-packet-filter.rules` reads nftables this way today, so the rule is in place there.
**Checked**: `merge-check.sh`: netcheck ok; `go vet`, `go test -race` green; new test: the command as root and through sudo.
mesh/merge-gate pass: builds netcheck → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
On novox the tool runner runs as the operator's account, and wg show
answered 'Operation not permitted'. Root is the module's concern: the
command runs as given when the process is root, else through sudo -n,
which the sudo module allows the runtime's account, as nftables does.
Deliverynovox/mesh-catalog@b1280f81a213 — delivered since 2026-10-11T22:13:35Z
Delivery plan — builds netcheck → ace, g14, novox, shanks; no bus step
tier 0: netcheck
ace: receives netcheck
g14: receives netcheck
novox: receives netcheck
shanks: receives netcheck
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 netcheck is judged on its first machine
Machines
netcheck on ace: passed — healthy 3 times over 2m28s
netcheck on the rest running it: sent
Transitions
2026-10-11 22:05 (new) → proposed (announced): novox/mesh-catalog#226's head announced
2026-10-11 22:07 proposed → checked (checked): the verdict names this commit
2026-10-11 22:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 22:09 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 22:09 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 22:13 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@b1280f81a213` — **delivered** since 2026-10-11T22:13:35Z
**Delivery plan** — builds netcheck → ace, g14, novox, shanks; no bus step
- tier 0: netcheck
- ace: receives netcheck
- g14: receives netcheck
- novox: receives netcheck
- shanks: receives netcheck
- 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 netcheck is judged on its first machine
**Machines**
- netcheck on ace: passed — healthy 3 times over 2m28s
- netcheck on the rest running it: sent
**Transitions**
- 2026-10-11 22:05 (new) → proposed (announced): novox/mesh-catalog#226's head announced
- 2026-10-11 22:07 proposed → checked (checked): the verdict names this commit
- 2026-10-11 22:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 22:09 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 22:09 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 22:13 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/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: netcheck)
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 netcheck → ace, g14, novox, shanks; no bus step
tier 0: netcheck
ace: receives netcheck
g14: receives netcheck
novox: receives netcheck
shanks: receives netcheck
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 netcheck is judged on its first machine
Run by the build seat on ace as build-1791756344260525610 (builds --log build-1791756344260525610).
--- the gate: netcheck
netcheck: ok, 5 tool(s)
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-11T22:02:09Z 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-11T22:02:09Z
modules the change moves:
- netcheck (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 1 module(s) in 1 tier(s): netcheck
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 42158 strings of 680 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s
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/netcheck
ok netcheck/cmd/netcheck 1.053s
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/netcheck (TypeScript)
testing modules/netcheck (TypeScript)
✔ only http and https URLs are checked (1.105859ms)
✔ only HEAD and GET are used (0.247195ms)
✔ a status, its headers and a redirect not followed (32.507008ms)
✔ a refused connection is a result with its error (3.573346ms)
ℹ tests 4
ℹ suites 0
ℹ pass 4
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 140.817569
**Merge check** at `b1280f81`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: netcheck)
- `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 netcheck → ace, g14, novox, shanks; no bus step
- tier 0: netcheck
- ace: receives netcheck
- g14: receives netcheck
- novox: receives netcheck
- shanks: receives netcheck
- 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 netcheck is judged on its first machine
Run by the build seat on ace as `build-1791756344260525610` (`builds --log build-1791756344260525610`).
```
--- the gate: netcheck
netcheck: ok, 5 tool(s)
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-11T22:02:09Z 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-11T22:02:09Z
modules the change moves:
- netcheck (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 1 module(s) in 1 tier(s): netcheck
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 42158 strings of 680 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s
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/netcheck
ok netcheck/cmd/netcheck 1.053s
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/netcheck (TypeScript)
testing modules/netcheck (TypeScript)
✔ only http and https URLs are checked (1.105859ms)
✔ only HEAD and GET are used (0.247195ms)
✔ a status, its headers and a redirect not followed (32.507008ms)
✔ a refused connection is a result with its error (3.573346ms)
ℹ tests 4
ℹ suites 0
ℹ pass 4
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 140.817569
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why (issue 522, after #225). On novox,
netcheck_tunnelansweredwg show mesh0: Unable to access interface: Operation not permitted: novox's tool runner runs as the operator's account, not root, and the tunnel answers only to root. #225 ranwgdirectly, so it worked only where the runner is root.What changes:
wgruns as given when the process is root, else throughsudo -n— the pattern the nftables module uses fornft(ADR 0175 §4: root is the module's concern; the sudo module allows the runtime's account without a prompt). A sudo refusal is said as such. novox's ownnode-packet-filter.rulesreads nftables this way today, so the rule is in place there.Checked:
merge-check.sh: netcheck ok;go vet,go test -racegreen; new test: the command as root and through sudo.Delivery
novox/mesh-catalog@b1280f81a213— delivered since 2026-10-11T22:13:35ZDelivery plan — builds netcheck → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
b1280f81mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: netcheck)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 netcheck → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791756344260525610(builds --log build-1791756344260525610).