mesh-cli: forward the line's standard input to the controller, with the line alone (hq ADR 0259 §10, ADR 0272) #73

Merged
mesh-admin merged 1 commits from feat/a-terminal-line-takes-standard-input into main 2026-10-09 15:58:48 +00:00
Contributor

Reviewers' checklist (the same on all four PRs)

  • Standard input is bounded at 64 KiB, refused over it by mesh-cli before asking and by every reader after (here: cli.ReadRequest).
  • It is given only to a line that runs as the controller's terminal; an ordinary call carrying it is refused and nothing runs (the controller's PR).
  • Never logged, never in the calls record, never in the journal, never in an answer, never resent with a follow.
  • On the bus it travels only inside the one core request on mesh.control..cli: no stream captures it, only the controller may subscribe it, and each hop is TLS to the pinned bus certificate. Not sealed end to end (the bus server holds it in memory while routing); sealing needs a controller key every engine knows, which does not exist.

This PR: Asked.Stdin (omitted when empty), filled from the request; a follow of the same call carries none; the engine says it nowhere. Test TestStandardInputGoesToTheControllerWithTheLineAndNowhereElse: through the real socket and AskTheController, the first request carries the input whole, the follow carries none, nothing the engine says contains it. mesh-sdk at f047d0a (mesh-sdk PR on the same branch name), to move to its tag.

sh merge-check.sh passes locally (bus tests skipped: no nats-server here). Do not merge without review.

**Reviewers' checklist (the same on all four PRs)** - Standard input is bounded at 64 KiB, refused over it by mesh-cli before asking and by every reader after (here: `cli.ReadRequest`). - It is given only to a line that runs as the controller's terminal; an ordinary call carrying it is refused and nothing runs (the controller's PR). - Never logged, never in the calls record, never in the journal, never in an answer, never resent with a follow. - On the bus it travels only inside the one core request on mesh.control.<node>.cli: no stream captures it, only the controller may subscribe it, and each hop is TLS to the pinned bus certificate. Not sealed end to end (the bus server holds it in memory while routing); sealing needs a controller key every engine knows, which does not exist. **This PR**: `Asked.Stdin` (omitted when empty), filled from the request; a follow of the same call carries none; the engine says it nowhere. Test `TestStandardInputGoesToTheControllerWithTheLineAndNowhereElse`: through the real socket and `AskTheController`, the first request carries the input whole, the follow carries none, nothing the engine says contains it. mesh-sdk at f047d0a (mesh-sdk PR on the same branch name), to move to its tag. `sh merge-check.sh` passes locally (bus tests skipped: no nats-server here). Do not merge without review.
mesh-admin added 1 commit 2026-10-09 14:51:10 +00:00
mesh-cli: forward the line's standard input to the controller, with the line alone
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 delivered
mesh/delivery-group group feat/a-terminal-line-takes-standard-input closed: a member was closed before the group merged
4ea6a2f04e
A secret given at the controller's terminal through mesh-cli (secret accept … --from -) never reached the
line: the engine forwarded the words only. It now forwards what mesh-cli's standard input held (at most
64 KiB, the SDK's bound) on the same core request to the controller, says it nowhere, and sends none
with a follow of the same call. mesh-sdk moves to f047d0a.
Author
Contributor

Delivery novox/mesh-host@4ea6a2f04e2c — delivered since 2026-10-09T16:03:02Z

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

Group feat/a-terminal-line-takes-standard-input, in order: novox/mesh-controller@07e59c535e → novox/mesh-host@4ea6a2f04e → novox/mesh-sdk@f047d0a4a9

Machines

  • mesh-host on ace: passed — healthy 3 times over 2m56s
  • mesh-host on the rest running it: sent

Transitions

  • 2026-10-09 14:51 (new) → proposed (announced): novox/mesh-host#73's head announced
  • 2026-10-09 14:53 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 14:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-09 15:59 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-09 15:59 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
  • 2026-10-09 16:03 delivering → delivered (done): its walk is done: 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-host@4ea6a2f04e2c` — **delivered** since 2026-10-09T16:03:02Z **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 **Group** `feat/a-terminal-line-takes-standard-input`, in order: novox/mesh-controller@07e59c535e7c → novox/mesh-host@4ea6a2f04e2c → novox/mesh-sdk@f047d0a4a970 - novox/mesh-controller@07e59c535e7c before novox/mesh-host@4ea6a2f04e2c: built by, over engine before controller - novox/mesh-controller@07e59c535e7c before novox/mesh-sdk@f047d0a4a970: built by - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-host on ace: passed — healthy 3 times over 2m56s - mesh-host on the rest running it: sent **Transitions** - 2026-10-09 14:51 (new) → proposed (announced): novox/mesh-host#73's head announced - 2026-10-09 14:53 proposed → checked (checked): the verdict names this commit - 2026-10-09 14:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 15:59 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 15:59 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 - 2026-10-09 16:03 delivering → delivered (done): its walk is done: 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 4ea6a2f0

  • 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 ace as build-1791557475928351617 (builds --log build-1791557475928351617).

--- the gate: mesh-host
mesh-host: ok
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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T14:42:25Z 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-09T14:42:25Z

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)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.11-0.20261009143344-f047d0a4a970
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.014s
ok  	github.com/novox/mesh-host/cmd/mesh-host	5.362s
ok  	github.com/novox/mesh-host/examples	1.034s
ok  	github.com/novox/mesh-host/internal/accounts	1.046s
ok  	github.com/novox/mesh-host/internal/apply	4.516s
ok  	github.com/novox/mesh-host/internal/bootstrap	1.494s
ok  	github.com/novox/mesh-host/internal/bundle	1.034s
ok  	github.com/novox/mesh-host/internal/declaration	1.062s
ok  	github.com/novox/mesh-host/internal/firewall	1.636s
ok  	github.com/novox/mesh-host/internal/identity	1.114s
ok  	github.com/novox/mesh-host/internal/image	1.026s
ok  	github.com/novox/mesh-host/internal/inventory	1.041s
ok  	github.com/novox/mesh-host/internal/link	10.337s
ok  	github.com/novox/mesh-host/internal/liveness	2.077s
ok  	github.com/novox/mesh-host/internal/meshcli	1.350s
ok  	github.com/novox/mesh-host/internal/network	1.063s
ok  	github.com/novox/mesh-host/internal/outward	1.045s
ok  	github.com/novox/mesh-host/internal/profile	1.526s
ok  	github.com/novox/mesh-host/internal/reachable	1.046s
ok  	github.com/novox/mesh-host/internal/store	1.213s
ok  	github.com/novox/mesh-host/internal/system	1.046s
ok  	github.com/novox/mesh-host/internal/tunnel	1.046s
ok  	github.com/novox/mesh-host/internal/units	1.042s
ok  	github.com/novox/mesh-host/internal/upgrade	1.132s
ok  	github.com/novox/mesh-host/internal/witness	4.364s
ok  	github.com/novox/mesh-host/packaging	1.011s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.010s
**Merge check** at `4ea6a2f0` - `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 ace as `build-1791557475928351617` (`builds --log build-1791557475928351617`). ``` --- the gate: mesh-host mesh-host: ok 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T14:42:25Z 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-09T14:42:25Z 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) go: downloading git.novox.be/novox/mesh-sdk/go v0.1.11-0.20261009143344-f047d0a4a970 ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s ok github.com/novox/mesh-host/cmd/mesh-host 5.362s ok github.com/novox/mesh-host/examples 1.034s ok github.com/novox/mesh-host/internal/accounts 1.046s ok github.com/novox/mesh-host/internal/apply 4.516s ok github.com/novox/mesh-host/internal/bootstrap 1.494s ok github.com/novox/mesh-host/internal/bundle 1.034s ok github.com/novox/mesh-host/internal/declaration 1.062s ok github.com/novox/mesh-host/internal/firewall 1.636s ok github.com/novox/mesh-host/internal/identity 1.114s ok github.com/novox/mesh-host/internal/image 1.026s ok github.com/novox/mesh-host/internal/inventory 1.041s ok github.com/novox/mesh-host/internal/link 10.337s ok github.com/novox/mesh-host/internal/liveness 2.077s ok github.com/novox/mesh-host/internal/meshcli 1.350s ok github.com/novox/mesh-host/internal/network 1.063s ok github.com/novox/mesh-host/internal/outward 1.045s ok github.com/novox/mesh-host/internal/profile 1.526s ok github.com/novox/mesh-host/internal/reachable 1.046s ok github.com/novox/mesh-host/internal/store 1.213s ok github.com/novox/mesh-host/internal/system 1.046s ok github.com/novox/mesh-host/internal/tunnel 1.046s ok github.com/novox/mesh-host/internal/units 1.042s ok github.com/novox/mesh-host/internal/upgrade 1.132s ok github.com/novox/mesh-host/internal/witness 4.364s ok github.com/novox/mesh-host/packaging 1.011s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.010s ```
mesh-admin merged commit b0d03be7a4 into main 2026-10-09 15:58:48 +00:00
mesh-admin deleted branch feat/a-terminal-line-takes-standard-input 2026-10-09 15:58:48 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-host#73