novox/mesh-catalog
8
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

The clipboard service waits for an older daemon's lock, and the history sees the daemon (hq issues 860, 862) #323

Merged
mesh-tools merged 3 commits from fix/860-862-the-clipboard-takes-over-quietly into main 2026-10-15 21:31:47 +00:00
Conversation 3 Commits 3 Files Changed 4
+116 -2
mesh-tools commented 2026-10-15 21:21:13 +00:00
Member
Copy Link
Copy Source

Fixes hq issues 862 and 860 together (playbook 08, related issues in one module).

862, the restart loop. After #320 was delivered without a new login, the session's older clipmenud held clipmenud's session lock; the user unit's launcher exec'd clipmenud, which exited 2 ("Can't lock session file") and the unit restarted every 2 s (196 restarts on g14). The launcher now probes the same lock file clipmenud takes (${CM_DIR:-${XDG_RUNTIME_DIR-${TMPDIR-/tmp}}}/clipmenu.6.$USER/session_lock) with flock -n -E 75 and waits quietly, 2 s per pass, while it is held; any other outcome (free, missing flock, missing file) starts clipmenud, so it never hangs. A delivery now takes over from an older daemon without a login and without a loop.

860, collecting:false while the daemon runs. clipmenud is a bash script, so its process's comm is bash (live on shanks: pid with cmdline bash /usr/bin/clipmenud). processesOf now also counts a process whose argv[0] is an interpreter and whose argv[1]'s basename is the name; still filtered by uid.

Tests: the real launcher waits silently while a holder keeps the lock and starts within 5 s of its release; collecting is true for bash /usr/bin/clipmenud and false for another script. go vet, go test -race -count=3, and merge-check.sh with a controller built from main (long-running resources without health: 62, as kept) pass.

Reviewed independently before push: APPROVE at 21ebbff. Nit noted, not blocking: clipboard_test.go ignores one os.WriteFile error.

Fixes hq issues 862 and 860 together (playbook 08, related issues in one module). **862, the restart loop.** After #320 was delivered without a new login, the session's older clipmenud held clipmenud's session lock; the user unit's launcher exec'd clipmenud, which exited 2 ("Can't lock session file") and the unit restarted every 2 s (196 restarts on g14). The launcher now probes the same lock file clipmenud takes (`${CM_DIR:-${XDG_RUNTIME_DIR-${TMPDIR-/tmp}}}/clipmenu.6.$USER/session_lock`) with `flock -n -E 75` and waits quietly, 2 s per pass, while it is held; any other outcome (free, missing flock, missing file) starts clipmenud, so it never hangs. A delivery now takes over from an older daemon without a login and without a loop. **860, collecting:false while the daemon runs.** clipmenud is a bash script, so its process's comm is `bash` (live on shanks: pid with cmdline `bash /usr/bin/clipmenud`). `processesOf` now also counts a process whose argv[0] is an interpreter and whose argv[1]'s basename is the name; still filtered by uid. Tests: the real launcher waits silently while a holder keeps the lock and starts within 5 s of its release; collecting is true for `bash /usr/bin/clipmenud` and false for another script. go vet, go test -race -count=3, and merge-check.sh with a controller built from main (long-running resources without health: 62, as kept) pass. Reviewed independently before push: APPROVE at 21ebbff. Nit noted, not blocking: clipboard_test.go ignores one os.WriteFile error.
mesh-tools added 2 commits 2026-10-15 21:21:13 +00:00
Wait quietly for clipmenud's session lock; count the operator's clipmenud (issues 860, 862) cf304d8629
Count clipmenud when it runs as a bash script (issue 860)
mesh/merge-gate head 21ebbffed469 merged into trunk 8c2d7e5f97f1 — pass: builds clipmenu → g14, shanks; no bus step; every machine composes with the change…
Details
mesh/repo-check head 21ebbffed469 merged into trunk 8c2d7e5f97f1 — fail: its merge-check.sh failed: --- FAIL: TestTheLauncherWaitsQuietlyWhileAnotherClipme…
Details
mesh/delivery superseded: a newer head of the same pull request
Details
21ebbffed4
mesh-tools commented 2026-10-15 21:21:24 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@6112233649d3 — delivered since 2026-10-15T21:33:31Z

Delivery plan — builds clipmenu → g14, shanks; no bus step

  • tier 0: clipmenu
  • g14: receives clipmenu
  • shanks: receives clipmenu
  • 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 clipmenu is judged on its first machine

Machines

  • clipmenu on every machine running it: sent

Transitions

  • 2026-10-15 21:28 (new) → proposed (announced): novox/mesh-catalog#323's head announced
  • 2026-10-15 21:31 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-15 21:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-15 21:31 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-15 21:31 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-15 21:33 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@6112233649d3` — **delivered** since 2026-10-15T21:33:31Z **Delivery plan** — builds clipmenu → g14, shanks; no bus step - tier 0: clipmenu - g14: receives clipmenu - shanks: receives clipmenu - 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 clipmenu is judged on its first machine **Machines** - clipmenu on every machine running it: sent **Transitions** - 2026-10-15 21:28 (new) → proposed (announced): novox/mesh-catalog#323's head announced - 2026-10-15 21:31 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-15 21:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-15 21:31 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-15 21:31 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-15 21:33 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-tools commented 2026-10-15 21:24:00 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 21ebbffe
Judged: head 21ebbffed469 merged into trunk 8c2d7e5f97f1; read beside it: mesh-controller 7543f64911c5, mesh-controller-main 7543f64911c5, mesh-host 198fd34ec497, mesh-tools 6b3e15042fee

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: clipmenu)
  • mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheLauncherWaitsQuietlyWhileAnotherClipmenudHoldsTheLock (0.01s)

Delivery plan — builds clipmenu → g14, shanks; no bus step

  • tier 0: clipmenu
  • g14: receives clipmenu
  • shanks: receives clipmenu
  • 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 clipmenu is judged on its first machine
  • read by no module's build: modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go, modules/clipmenu/cmd/clipmenu-tools/manifest_test.go

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

--- the gate: clipmenu
clipmenu: ok, 3 tool(s), ready: daemon 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-15T21:07:28Z 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-15T21:07:28Z

modules the change moves:
  - clipmenu (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): clipmenu

notes:
  - modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go and modules/clipmenu/cmd/clipmenu-tools/manifest_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 48788 strings of 747 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/mailstore	0.010s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.013s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
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: 62, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.218s
testing modules/clipmenu
--- FAIL: TestTheLauncherWaitsQuietlyWhileAnotherClipmenudHoldsTheLock (0.01s)
    manifest_test.go:194: the launcher went on while the lock was held: "flock: unrecognized option: E\nBusyBox v1.37.0 (2026-01-10 15:38:28 UTC) multi-call binary.\n\nUsage: flock [-sxun] FD | { FILE [-c] PROG ARGS }\n\n[Un]lock file descriptor, or lock FILE, run PROG\n\n\t-s\tShared lock\n\t-x\tExclusive lock (default)\n\t-u\tUnlock FD\n\t-n\tFail rather than wait\nstarted\n"
FAIL
FAIL	clipmenu/cmd/clipmenu-tools	8.299s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheLauncherWaitsQuietlyWhileAnotherClipmenudHoldsTheLock (0.01s)
    manifest_test.go:194: the launcher went on while the lock was held: "flock: unrecognized option: E\nBusyBox v1.37.0 (2026-01-10 15:38:28 UTC) multi-call binary.\n\nUsage: flock [-sxun] FD | { FILE [-c] PROG ARGS }\n\n[Un]lock file descriptor, or lock FILE, run PROG\n\n\t-s\tShared lock\n\t-x\tExclusive lock (default)\n\t-u\tUnlock FD\n\t-n\tFail rather than wait\nstarted\n"
FAIL	clipmenu/cmd/clipmenu-tools	8.299s
**Merge check** at `21ebbffe` Judged: head `21ebbffed469` merged into trunk `8c2d7e5f97f1`; read beside it: mesh-controller `7543f64911c5`, mesh-controller-main `7543f64911c5`, mesh-host `198fd34ec497`, mesh-tools `6b3e15042fee` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: clipmenu) - `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheLauncherWaitsQuietlyWhileAnotherClipmenudHoldsTheLock (0.01s) **Delivery plan** — builds clipmenu → g14, shanks; no bus step - tier 0: clipmenu - g14: receives clipmenu - shanks: receives clipmenu - 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 clipmenu is judged on its first machine - read by no module's build: modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go, modules/clipmenu/cmd/clipmenu-tools/manifest_test.go Run by the build seat on shanks as `build-1792099276914191222` (`builds --log build-1792099276914191222`). ``` --- the gate: clipmenu clipmenu: ok, 3 tool(s), ready: daemon 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-15T21:07:28Z 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-15T21:07:28Z modules the change moves: - clipmenu (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): clipmenu notes: - modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go and modules/clipmenu/cmd/clipmenu-tools/manifest_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 48788 strings of 747 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/mailstore 0.010s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.013s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) 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: 62, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.218s testing modules/clipmenu --- FAIL: TestTheLauncherWaitsQuietlyWhileAnotherClipmenudHoldsTheLock (0.01s) manifest_test.go:194: the launcher went on while the lock was held: "flock: unrecognized option: E\nBusyBox v1.37.0 (2026-01-10 15:38:28 UTC) multi-call binary.\n\nUsage: flock [-sxun] FD | { FILE [-c] PROG ARGS }\n\n[Un]lock file descriptor, or lock FILE, run PROG\n\n\t-s\tShared lock\n\t-x\tExclusive lock (default)\n\t-u\tUnlock FD\n\t-n\tFail rather than wait\nstarted\n" FAIL FAIL clipmenu/cmd/clipmenu-tools 8.299s FAIL --- what failed, picked from the whole of its output (the whole is in the build's log) --- FAIL: TestTheLauncherWaitsQuietlyWhileAnotherClipmenudHoldsTheLock (0.01s) manifest_test.go:194: the launcher went on while the lock was held: "flock: unrecognized option: E\nBusyBox v1.37.0 (2026-01-10 15:38:28 UTC) multi-call binary.\n\nUsage: flock [-sxun] FD | { FILE [-c] PROG ARGS }\n\n[Un]lock file descriptor, or lock FILE, run PROG\n\n\t-s\tShared lock\n\t-x\tExclusive lock (default)\n\t-u\tUnlock FD\n\t-n\tFail rather than wait\nstarted\n" FAIL clipmenu/cmd/clipmenu-tools 8.299s ```
jschoubben added 1 commit 2026-10-15 21:28:31 +00:00
Probe clipmenud's lock with flock's default conflict status, which BusyBox shares (issue 862)
mesh/merge-gate head 6112233649d3 merged into trunk 8c2d7e5f97f1 — pass: builds clipmenu → g14, shanks; no bus step; every machine composes with the change…
Details
mesh/repo-check head 6112233649d3 merged into trunk 8c2d7e5f97f1 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Details
mesh/delivery delivered
Details
6112233649
mesh-tools commented 2026-10-15 21:31:41 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 61122336
Judged: head 6112233649d3 merged into trunk 8c2d7e5f97f1; read beside it: mesh-controller 7543f64911c5, mesh-controller-main 7543f64911c5, mesh-host 198fd34ec497, mesh-tools 6b3e15042fee

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

  • tier 0: clipmenu
  • g14: receives clipmenu
  • shanks: receives clipmenu
  • 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 clipmenu is judged on its first machine
  • read by no module's build: modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go, modules/clipmenu/cmd/clipmenu-tools/manifest_test.go

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

--- the gate: clipmenu
clipmenu: ok, 3 tool(s), ready: daemon 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-15T21:27:28Z 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-15T21:27:28Z

modules the change moves:
  - clipmenu (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): clipmenu

notes:
  - modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go and modules/clipmenu/cmd/clipmenu-tools/manifest_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 48788 strings of 747 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.015s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.010s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.015s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.007s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 62, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.314s
testing modules/clipmenu
ok  	clipmenu/cmd/clipmenu-tools	13.326s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `61122336` Judged: head `6112233649d3` merged into trunk `8c2d7e5f97f1`; read beside it: mesh-controller `7543f64911c5`, mesh-controller-main `7543f64911c5`, mesh-host `198fd34ec497`, mesh-tools `6b3e15042fee` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: clipmenu) - `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 clipmenu → g14, shanks; no bus step - tier 0: clipmenu - g14: receives clipmenu - shanks: receives clipmenu - 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 clipmenu is judged on its first machine - read by no module's build: modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go, modules/clipmenu/cmd/clipmenu-tools/manifest_test.go Run by the build seat on novox as `build-1792099713060421882` (`builds --log build-1792099713060421882`). ``` --- the gate: clipmenu clipmenu: ok, 3 tool(s), ready: daemon 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-15T21:27:28Z 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-15T21:27:28Z modules the change moves: - clipmenu (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): clipmenu notes: - modules/clipmenu/cmd/clipmenu-tools/clipboard_test.go and modules/clipmenu/cmd/clipmenu-tools/manifest_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 48788 strings of 747 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.015s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.010s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.015s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/paths 0.007s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 62, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.314s testing modules/clipmenu ok clipmenu/cmd/clipmenu-tools 13.326s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools merged commit 6a5e6510ca into main 2026-10-15 21:31:47 +00:00
mesh-tools deleted branch fix/860-862-the-clipboard-takes-over-quietly 2026-10-15 21:31:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jschoubben mesh-tools miel.truyen
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#323