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

2 Commits

Author	SHA1	Message	Date
jochen	31120ed580	mesh-mail-notifier: watch retries a subscribe refusal instead of exiting (issue 859, review round 1) ... 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).	2026-10-15 23:17:14 +02:00
jochen	12d7852082	mesh-mail-notifier: the watcher runs in the base invocation, not a separate notify process (issue 859) ... 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.	2026-10-15 23:13:34 +02:00