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

mesh-mail-notifier: the watcher runs in its runtime, not a process that exits at once (issue 859) #322

Merged
mesh-tools merged 2 commits from fix/859-notifier-runs-in-its-runtime into main 2026-10-15 21:21:13 +00:00
Conversation 2 Commits 2 Files Changed 5
+191 -39
mesh-tools commented 2026-10-15 21:17:53 +00:00
Member
Copy Link
Copy Source

Issue 859 (playbook 08). mesh-mail-notifier's notify process started the watcher and then served MCP over stdin; under systemd stdin is empty, so it returned at EOF and exited 0 every 5 s (400+ restarts on g14), and no notice was ever shown. The watcher now runs in the base invocation the node's runtime launches and keeps alive (as mesh-knowledge's hear and messenger do), the notify process resource is gone, and a refused subscribe is retried with backoff (2 s doubling to 1 min), logged, never exiting.

Tests: the startup path at stdin EOF keeps the watcher running (ping/pong); a subscribe refused twice then accepted leaves the process serving; no process resource is declared. Each failed before the change.

Reviewed locally: round 1 approve with a change (retry instead of exit, a vacuous test), round 2 approved at 31120ed. merge-check.sh green with MESH_GATE from mesh-controller main.

Issue 859 (playbook 08). mesh-mail-notifier's `notify` process started the watcher and then served MCP over stdin; under systemd stdin is empty, so it returned at EOF and exited 0 every 5 s (400+ restarts on g14), and no notice was ever shown. The watcher now runs in the base invocation the node's runtime launches and keeps alive (as mesh-knowledge's hear and messenger do), the `notify` process resource is gone, and a refused subscribe is retried with backoff (2 s doubling to 1 min), logged, never exiting. Tests: the startup path at stdin EOF keeps the watcher running (ping/pong); a subscribe refused twice then accepted leaves the process serving; no process resource is declared. Each failed before the change. Reviewed locally: round 1 approve with a change (retry instead of exit, a vacuous test), round 2 approved at 31120ed. merge-check.sh green with MESH_GATE from mesh-controller main.
mesh-tools added 2 commits 2026-10-15 21:17:53 +00:00
mesh-mail-notifier: the watcher runs in the base invocation, not a separate notify process (issue 859) 12d7852082 
The notify process's stdin is empty under systemd, so stdio.Serve returned at EOF, main returned, and
systemd restarted it every five seconds: the watch loop never ran long enough to show a notice. The watch
loop now starts beside stdio.Serve in the one process the node's runtime launches and keeps alive, as
mesh-knowledge's serve does. No resource declares a separate notify process any more.
mesh-mail-notifier: watch retries a subscribe refusal instead of exiting (issue 859, review round 1)
mesh/merge-gate head 31120ed58029 merged into trunk c9848f4fb85c — pass: builds mesh-mail-notifier → g14, shanks; no bus step; every machine composes with …
Details
mesh/repo-check head 31120ed58029 merged into trunk c9848f4fb85c — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Details
mesh/delivery delivered
Details
31120ed580 
A subscribe the runtime refuses no longer calls os.Exit(1), which took mail-notifier.status and
mail_notifier_health down with it: watch now retries with backoff (2s doubling to 1 minute), logging each
refusal, as mesh-knowledge's hear does. Also: the run() test proves liveness by having the watcher answer a
ping after run returns, instead of checking a channel only the test's own deferred cleanup could close; and
the manifest test is renamed to say what it checks (no process resource at all).
mesh-tools commented 2026-10-15 21:17:56 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@31120ed58029 — delivered since 2026-10-15T21:23:01Z

Delivery plan — builds mesh-mail-notifier → g14, shanks; no bus step

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

Machines

  • mesh-mail-notifier on every machine running it: sent

Transitions

  • 2026-10-15 21:17 (new) → proposed (announced): novox/mesh-catalog#322's head announced
  • 2026-10-15 21:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-15 21:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-15 21:21 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:21 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:23 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@31120ed58029` — **delivered** since 2026-10-15T21:23:01Z **Delivery plan** — builds mesh-mail-notifier → g14, shanks; no bus step - tier 0: mesh-mail-notifier - g14: receives mesh-mail-notifier - shanks: receives mesh-mail-notifier - 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 mesh-mail-notifier is judged on its first machine **Machines** - mesh-mail-notifier on every machine running it: sent **Transitions** - 2026-10-15 21:17 (new) → proposed (announced): novox/mesh-catalog#322's head announced - 2026-10-15 21:20 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-15 21:20 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-15 21:21 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:21 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:23 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:20:44 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 31120ed5
Judged: head 31120ed58029 merged into trunk c9848f4fb85c; 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: mesh-mail-notifier)
  • 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 mesh-mail-notifier → g14, shanks; no bus step

  • tier 0: mesh-mail-notifier
  • g14: receives mesh-mail-notifier
  • shanks: receives mesh-mail-notifier
  • 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 mesh-mail-notifier is judged on its first machine
  • read by no module's build: modules/mesh-mail-notifier/README.md, modules/mesh-mail-notifier/cmd/mesh-mail-notifier/manifest_test.go, modules/mesh-mail-notifier/cmd/mesh-mail-notifier/run_test.go

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

--- the gate: mesh-mail-notifier
note: mesh-mail-notifier claims the seat "mail-notifier", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-mail-notifier: ok, 2 tool(s), invokes seat:node-notifier.send, seat:mail-store.accounts, keeps state shown
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:
  - mesh-mail-notifier (changed)

machines:
  - a machine (f35): composes; the change adds 0 resource(s) and removes 1 (-process:mesh-mail-notifier.notify)
  - 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; the change adds 0 resource(s) and removes 1 (-process:mesh-mail-notifier.notify)

a merge would rebuild 1 module(s) in 1 tier(s): mesh-mail-notifier

notes:
  - modules/mesh-mail-notifier/README.md, modules/mesh-mail-notifier/cmd/mesh-mail-notifier/manifest_test.go and modules/mesh-mail-notifier/cmd/mesh-mail-notifier/run_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 48780 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.014s
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.219s
testing modules/mesh-mail-notifier
ok  	mesh-mail-notifier/cmd/mesh-mail-notifier	1.015s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `31120ed5` Judged: head `31120ed58029` merged into trunk `c9848f4fb85c`; 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: mesh-mail-notifier) - `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 mesh-mail-notifier → g14, shanks; no bus step - tier 0: mesh-mail-notifier - g14: receives mesh-mail-notifier - shanks: receives mesh-mail-notifier - 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 mesh-mail-notifier is judged on its first machine - read by no module's build: modules/mesh-mail-notifier/README.md, modules/mesh-mail-notifier/cmd/mesh-mail-notifier/manifest_test.go, modules/mesh-mail-notifier/cmd/mesh-mail-notifier/run_test.go Run by the build seat on shanks as `build-1792099075351455794` (`builds --log build-1792099075351455794`). ``` --- the gate: mesh-mail-notifier note: mesh-mail-notifier claims the seat "mail-notifier", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here mesh-mail-notifier: ok, 2 tool(s), invokes seat:node-notifier.send, seat:mail-store.accounts, keeps state shown 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: - mesh-mail-notifier (changed) machines: - a machine (f35): composes; the change adds 0 resource(s) and removes 1 (-process:mesh-mail-notifier.notify) - 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; the change adds 0 resource(s) and removes 1 (-process:mesh-mail-notifier.notify) a merge would rebuild 1 module(s) in 1 tier(s): mesh-mail-notifier notes: - modules/mesh-mail-notifier/README.md, modules/mesh-mail-notifier/cmd/mesh-mail-notifier/manifest_test.go and modules/mesh-mail-notifier/cmd/mesh-mail-notifier/run_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 48780 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.014s 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.219s testing modules/mesh-mail-notifier ok mesh-mail-notifier/cmd/mesh-mail-notifier 1.015s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools merged commit 8c2d7e5f97 into main 2026-10-15 21:21:13 +00:00
mesh-tools deleted branch fix/859-notifier-runs-in-its-runtime 2026-10-15 21:21:13 +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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#322