Issue 315: a failed unit of a module was never raised #199

2026-10-08T09:30:36Z

mesh-admin commented

2026-10-08 09:30:36 +00:00

Registers issue 315 (playbook 03), status located.

A module's daemon shipped as a package's unit (the Razer daemon, D-Bus activated) failed at every login on both workstations while the machine read healthy; liveness judges only long-running resources, and the profile's service-manager degraded was raised by nothing. Two mounts of the operator's own mount table and a leftover clipboard unit failed beside it, also unsaid.

Fix: novox/mesh-host PR #53 (the node-engine reads failed units and says whose each is) and novox/mesh-controller PR #137 (module condition names the unit; one machine.<m>.units warning for the machine's own). replay: to be named at resolution (core issue, ADR 0237).

Registers issue 315 (playbook 03), status `located`. A module's daemon shipped as a package's unit (the Razer daemon, D-Bus activated) failed at every login on both workstations while the machine read healthy; liveness judges only long-running resources, and the profile's `service-manager degraded` was raised by nothing. Two mounts of the operator's own mount table and a leftover clipboard unit failed beside it, also unsaid. Fix: novox/mesh-host PR #53 (the node-engine reads failed units and says whose each is) and novox/mesh-controller PR #137 (module condition names the unit; one `machine.<m>.units` warning for the machine's own). `replay:` to be named at resolution (core issue, ADR 0237).

mesh-admin added 2 commits 2026-10-08 09:30:36 +00:00

Issue 315: a failed unit of a module was never raised 7121d0737e

Liveness judged only long-running resources, so a module whose daemon
is a package's unit failed at every login while its machine read
healthy, and a degraded service manager was said by nothing.

Issue 315: say the node-engine's repository as an identifier

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

28aabd8621

mesh-admin commented

2026-10-08 09:30:51 +00:00

Delivery novox/hq@28aabd8621ae — delivered since 2026-10-08T09:40:30Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-08 09:30 (new) → proposed (announced): novox/hq#199's head announced
2026-10-08 09:32 proposed → checked (checked): the verdict names this commit
2026-10-08 09:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 09:40 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 09:40 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@28aabd8621ae` — **delivered** since 2026-10-08T09:40:30Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 09:30 (new) → proposed (announced): novox/hq#199's head announced - 2026-10-08 09:32 proposed → checked (checked): the verdict names this commit - 2026-10-08 09:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 09:40 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 09:40 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin merged commit f2201beb40 into main

2026-10-08 09:40:28 +00:00

mesh-admin deleted branch issues/315-a-failed-unit-was-never-raised

2026-10-08 09:40:29 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#199