dunst: reload the running notifier when the mesh rewrites its file #144

Merged
mesh-admin merged 1 commits from fix/dunst-reloads-when-its-file-changes into main 2026-10-08 20:12:23 +00:00
Contributor

Why

A setting changed through mesh-controller.settings (hq ADR 0262) rewrote ~/.config/dunst/dunstrc, but the running dunst kept the old font and width until the next login: the module declared no unit, so nothing told dunst its file changed.

What

  • module.json: a service resource notifier for the package's own dunst.service, in the account's manager (scope: user, user: ${machine:account}, hq ADR 0177), without a state (hq ADR 0117: its lifecycle stays the bus's; the node-engine never starts, stops or enables it), with reload-on: [configuration]. When the push rewrites dunstrc and dunst is running, the node-engine runs systemctl --user --machine=<account>@ reload dunst.service, whose packaged ExecReload is dunstctl reload (dunst 1.13.2). A reload keeps what is on screen and in the history; a restart would drop them. Not running: left alone, it reads the file when the bus starts it. Stateless, so not a long-running resource: the health count stays 70.
  • New tool dunst_reload: reloads now, checks dunst still answers, and answers the files read plus the [global] font, font size and width they set and which file set each (dunst does not expose its settings over the bus, so they are read from the same files, last file wins; a rule's own font is ignored).
  • files/dunstrc header says the file is reloaded on change. This also changes the file on every machine, so the first rollout itself reloads every running dunst.
  • README and the manifest test's rule "nothing starts it but the bus" now allow exactly a stateless unit.

Checked

  • Tests written first (reload_test.go): failed (build, then no resource "notifier"), now pass under -race.
  • merge-check.sh with MESH_CHECK_MODULES=dunst and the controller at main (8170fc5): words, paths, module check all clean; resources without health 70, as kept; dunst tests ok.

Acceptance (after merge and rollout, on the laptop)

Change font-size / width through mesh-controller.settings, push the laptop, send a sticky notification: it shows at the new size without a logout. dunst_reload answers the font/width in force from the files.

## Why A setting changed through `mesh-controller.settings` (hq ADR 0262) rewrote `~/.config/dunst/dunstrc`, but the running dunst kept the old font and width until the next login: the module declared no unit, so nothing told dunst its file changed. ## What - `module.json`: a service resource `notifier` for the package's own `dunst.service`, in the account's manager (`scope: user`, `user: ${machine:account}`, hq ADR 0177), **without a state** (hq ADR 0117: its lifecycle stays the bus's; the node-engine never starts, stops or enables it), with `reload-on: [configuration]`. When the push rewrites dunstrc and dunst is running, the node-engine runs `systemctl --user --machine=<account>@ reload dunst.service`, whose packaged `ExecReload` is `dunstctl reload` (dunst 1.13.2). A reload keeps what is on screen and in the history; a restart would drop them. Not running: left alone, it reads the file when the bus starts it. Stateless, so not a long-running resource: the health count stays 70. - New tool `dunst_reload`: reloads now, checks dunst still answers, and answers the files read plus the `[global]` font, font size and width they set and which file set each (dunst does not expose its settings over the bus, so they are read from the same files, last file wins; a rule's own font is ignored). - `files/dunstrc` header says the file is reloaded on change. This also changes the file on every machine, so the first rollout itself reloads every running dunst. - README and the manifest test's rule "nothing starts it but the bus" now allow exactly a stateless unit. ## Checked - Tests written first (`reload_test.go`): failed (build, then `no resource "notifier"`), now pass under `-race`. - `merge-check.sh` with `MESH_CHECK_MODULES=dunst` and the controller at main (8170fc5): words, paths, module check all clean; resources without health 70, as kept; dunst tests ok. ## Acceptance (after merge and rollout, on the laptop) Change `font-size` / `width` through `mesh-controller.settings`, push the laptop, send a sticky notification: it shows at the new size without a logout. `dunst_reload` answers the font/width in force from the files.
mesh-admin added 1 commit 2026-10-08 20:08:36 +00:00
dunst: reload the running notifier when the mesh rewrites its file
mesh/delivery delivered
mesh/merge-gate pass: builds dunst → g14, 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
9d438184be
A setting changed through mesh-controller.settings rewrote dunstrc, but the
running dunst kept the old font and width until the next login. Declare the
package's dunst.service in the account's manager, without a state, with
reload-on the configuration, so the node-engine runs its ExecReload
(dunstctl reload) and what is on screen stays. Add dunst_reload to do the
same on demand and say the font and width the files set.
Author
Contributor

Delivery novox/mesh-catalog@9d438184be3c — delivered since 2026-10-08T20:15:55Z

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

  • tier 0: dunst
  • g14: receives dunst
  • shanks: receives dunst

Machines

  • dunst on g14: passed — healthy 3 times over 2m41s
  • dunst on the rest running it: sent

Transitions

  • 2026-10-08 20:08 (new) → proposed (announced): novox/mesh-catalog#144's head announced
  • 2026-10-08 20:11 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 20:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 20:12 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-08 20:12 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-08 20:15 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-catalog@9d438184be3c` — **delivered** since 2026-10-08T20:15:55Z **Delivery plan** — builds dunst → g14, shanks; no bus step - tier 0: dunst - g14: receives dunst - shanks: receives dunst **Machines** - dunst on g14: passed — healthy 3 times over 2m41s - dunst on the rest running it: sent **Transitions** - 2026-10-08 20:08 (new) → proposed (announced): novox/mesh-catalog#144's head announced - 2026-10-08 20:11 proposed → checked (checked): the verdict names this commit - 2026-10-08 20:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 20:12 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 20:12 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-08 20:15 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 9d438184

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst)
  • mesh/repo-check: PASS — its merge-check.sh passed

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

  • tier 0: dunst
  • g14: receives dunst
  • shanks: receives dunst

Run by the build seat on g14 as build-1791490119438713732 (builds --log build-1791490119438713732).

--- the gate: dunst
dunst: ok, 6 tool(s)
long-running resources without health: 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-08T19:59:18Z 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-08T19:59:18Z

modules the change moves:
  - dunst (changed)

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

a merge would rebuild 1 module(s) in 1 tier(s): dunst
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 32506 strings of 585 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/dunst
ok  	dunst/cmd/dunst-tools	3.073s
**Merge check** at `9d438184` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: dunst) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds dunst → g14, shanks; no bus step - tier 0: dunst - g14: receives dunst - shanks: receives dunst Run by the build seat on g14 as `build-1791490119438713732` (`builds --log build-1791490119438713732`). ``` --- the gate: dunst dunst: ok, 6 tool(s) long-running resources without health: 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-08T19:59:18Z 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-08T19:59:18Z modules the change moves: - dunst (changed) machines: - a machine (f35): composes; the change adds 1 resource(s) and removes 0 (+service:dunst.notifier) - 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 1 resource(s) and removes 0 (+service:dunst.notifier) a merge would rebuild 1 module(s) in 1 tier(s): dunst --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 32506 strings of 585 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/dunst ok dunst/cmd/dunst-tools 3.073s ```
mesh-admin merged commit 8131aa390f into main 2026-10-08 20:12:23 +00:00
mesh-admin deleted branch fix/dunst-reloads-when-its-file-changes 2026-10-08 20:12:24 +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-catalog#144