A channel shows nothing from its memory after a restart; the router says again what is still open (issue 384) #182

Merged
mesh-admin merged 2 commits from fix/issue-384-restart-replays-nothing into main 2026-10-10 14:17:04 +00:00
Contributor

Fixes issue 384 (the tracker's): a restarted desk notifier re-showed nine old popups — resolved, silenced and cancelled ones included.

Cause

The desk's rule "a notifier that started again is shown again every open message with buttons it showed" replayed the desk's own memory on dunst.started (the desk-channel's journal: the notifier on g14 at 15:46, on shanks at 15:49). That memory held every handle ever shown with buttons (30-day TTL); before #176 each reminder and escalation had a handle of its own, and the router's edits (silenced, resolved) reached only the newest handle of a problem, so the older ones stood as if open. The channel's memory was taken as the truth about what is open; only the router knows that.

Fix

desk-channel

  • Started shows nothing. It forgets the machine's notification ids in every remembered message (so an edit changes nothing there and a message said again is shown anew), and says the standing at once with shows-since = when that screen became new. The same start event is acted on once.
  • The memory is used only to replace or edit in place (unchanged).
  • An edit without buttons that reaches no screen its message is on is taken with nothing to change (no failed); one with buttons that reaches no screen stays a failure, so the router says it anew.
  • Standing is the SDK's asks.Standing plus shows-since (JSON). The field belongs in asks.Standing in mesh-sdk; a follow-up.

messenger (restart.go)

  • Stand(kind, s): a shows-since later than the one last acted on (or, on a kind's first word, later than this router's start) is a screen made new. It waits while the kind cannot send (not pushed to Telegram as a failed delivery would be).
  • reoffer: on that kind only, for each record shown there as a message of its own: open and asked there → said again under its handle through the outbox (one message per problem, the current words and tickets; forced flush, not the desk's 15-min warning rhythm); silenced → edited to the silenced wording, no buttons, no urgency; ended → nothing. Logged and recorded in the history as (screen).
  • Telegram re-shows nothing on restart (checked: its Take acts only on work; its chat keeps the messages) and says no shows-since.

ADR 0258/0259 kept: the desk carries acknowledgements only; tickets are per ask, option and kind, one-time; a re-offer carries the ask's unused tickets, mints no new ones. ADR 0258's check line "offered the open answers with fresh tokens, the old ones refused" predates ADR 0259's tickets; under it the tickets are bound to the ask, and the test shows one warrant per ticket however often it is tapped — worth a progressive insight on ADR 0258 in hq.

Tests

  • messenger/restart_test.go: four records on the desk (open+asked, silenced+asked, open+nothing asked, resolved): the standing with shows-since yields one Replace under the open one's handle with its Silence ticket, one edit of the silenced one to the silenced words (no actions, quiet, not urgent), nothing for the resolved and the merely-open one, nothing on Telegram; a repeated or older shows-since yields nothing more; the ticket gives one warrant, and is refused from another machine. A second test: a shows-since before the router's start, Telegram's standing, and a desk that cannot send (waits; said once it can; never to Telegram).
  • Mutation on the replay branch (five mutants of restart.go, each killed by the tests): resolved re-offered; repeated standing re-offers; every open message re-offered, not only asked; silenced re-offered with buttons; not-ready desk not waited for.
  • desk-channel/desk_test.go: three remembered messages (open, silenced, resolved) on the machine; after Started nothing is shown, the ids are forgotten, the standing carries shows-since; the router's show under the open handle is shown anew (no replace_id) and clickable; the edit of the silenced one shows nothing and fails nothing; an edit with buttons that reaches no screen is said failed; a redelivered start event does nothing.
  • merge-check.sh with the changed modules: words, agent-home, paths green; desk-channel and messenger vet + tests under -race green; telegram's tests green.
Fixes issue 384 (the tracker's): a restarted desk notifier re-showed nine old popups — resolved, silenced and cancelled ones included. ## Cause The desk's rule "a notifier that started again is shown again every open message with buttons it showed" replayed the desk's own memory on `dunst.started` (the desk-channel's journal: the notifier on g14 at 15:46, on shanks at 15:49). That memory held every handle ever shown with buttons (30-day TTL); before #176 each reminder and escalation had a handle of its own, and the router's edits (silenced, resolved) reached only the newest handle of a problem, so the older ones stood as if open. The channel's memory was taken as the truth about what is open; only the router knows that. ## Fix **desk-channel** - `Started` shows nothing. It forgets the machine's notification ids in every remembered message (so an edit changes nothing there and a message said again is shown anew), and says the standing at once with `shows-since` = when that screen became new. The same start event is acted on once. - The memory is used only to replace or edit in place (unchanged). - An `edit` without buttons that reaches no screen its message is on is taken with nothing to change (no `failed`); one with buttons that reaches no screen stays a failure, so the router says it anew. - `Standing` is the SDK's `asks.Standing` plus `shows-since` (JSON). The field belongs in `asks.Standing` in mesh-sdk; a follow-up. **messenger** (`restart.go`) - `Stand(kind, s)`: a `shows-since` later than the one last acted on (or, on a kind's first word, later than this router's start) is a screen made new. It waits while the kind cannot send (not pushed to Telegram as a failed delivery would be). - `reoffer`: on that kind only, for each record shown there as a message of its own: open and asked there → said again under its handle through the outbox (one message per problem, the current words and tickets; forced flush, not the desk's 15-min warning rhythm); silenced → edited to the silenced wording, no buttons, no urgency; ended → nothing. Logged and recorded in the history as `(screen)`. - Telegram re-shows nothing on restart (checked: its `Take` acts only on work; its chat keeps the messages) and says no `shows-since`. ADR 0258/0259 kept: the desk carries acknowledgements only; tickets are per ask, option and kind, one-time; a re-offer carries the ask's unused tickets, mints no new ones. ADR 0258's check line "offered the open answers with fresh tokens, the old ones refused" predates ADR 0259's tickets; under it the tickets are bound to the ask, and the test shows one warrant per ticket however often it is tapped — worth a progressive insight on ADR 0258 in hq. ## Tests - `messenger/restart_test.go`: four records on the desk (open+asked, silenced+asked, open+nothing asked, resolved): the standing with `shows-since` yields one `Replace` under the open one's handle with its Silence ticket, one edit of the silenced one to the silenced words (no actions, quiet, not urgent), nothing for the resolved and the merely-open one, nothing on Telegram; a repeated or older `shows-since` yields nothing more; the ticket gives one warrant, and is refused from another machine. A second test: a `shows-since` before the router's start, Telegram's standing, and a desk that cannot send (waits; said once it can; never to Telegram). - Mutation on the replay branch (five mutants of `restart.go`, each killed by the tests): resolved re-offered; repeated standing re-offers; every open message re-offered, not only asked; silenced re-offered with buttons; not-ready desk not waited for. - `desk-channel/desk_test.go`: three remembered messages (open, silenced, resolved) on the machine; after `Started` nothing is shown, the ids are forgotten, the standing carries `shows-since`; the router's `show` under the open handle is shown anew (no `replace_id`) and clickable; the edit of the silenced one shows nothing and fails nothing; an edit with buttons that reaches no screen is said failed; a redelivered start event does nothing. - `merge-check.sh` with the changed modules: words, agent-home, paths green; desk-channel and messenger vet + tests under `-race` green; telegram's tests green.
mesh-admin added 1 commit 2026-10-10 14:03:03 +00:00
A channel shows nothing from its memory after a restart; the router says again what is still open (issue 384)
mesh/merge-gate pass: builds desk-channel, messenger → novox; 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
cd85104988
On 2026-10-10 the desk's notifier started again on two machines and the desk showed, from its own
memory, nine old popups: resolved, silenced and cancelled ones among them. Its memory held every handle
ever shown with buttons, and the router's edits (silenced, resolved) had reached only the newest handle
of each problem, so the rest stood as if open.

A channel's memory serves only to replace or edit a message in place. A notifier that started again lost
its screen: the desk forgets that machine's notification ids and says in its standing since when the
screen is new (shows-since). The router, which alone knows what is still open and unanswered, says that
again on that kind: one message per problem under its handle with the words and answers of now, a
silenced one edited to say so with no answers and no urgency, nothing that ended. Each move of
shows-since is acted on once, and waits while the desk cannot send rather than going to Telegram.
Telegram re-shows nothing on a restart (its messages stay in the chat) and says no shows-since.

An edit that offers nothing and reaches no screen its message is on is taken with nothing to change;
one that offers answers is said as failed, so the router says it anew.
Author
Contributor

Delivery novox/mesh-catalog@45361b013a8d — delivered since 2026-10-10T14:23:01Z

Delivery plan — builds desk-channel, messenger → novox; no bus step

  • tier 0: desk-channel, messenger
  • novox: receives desk-channel, messenger

Machines

  • desk-channel on novox: passed — healthy 3 times over 3m18s
  • messenger on novox: passed — judged with desk-channel: healthy 3 times over 3m18s
  • desk-channel on the rest running it: sent
  • messenger on the rest running it: sent

Transitions

  • 2026-10-10 14:14 (new) → proposed (announced): novox/mesh-catalog#182's head announced
  • 2026-10-10 14:15 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 14:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 14:18 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 14:18 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-10 14: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@45361b013a8d` — **delivered** since 2026-10-10T14:23:01Z **Delivery plan** — builds desk-channel, messenger → novox; no bus step - tier 0: desk-channel, messenger - novox: receives desk-channel, messenger **Machines** - desk-channel on novox: passed — healthy 3 times over 3m18s - messenger on novox: passed — judged with desk-channel: healthy 3 times over 3m18s - desk-channel on the rest running it: sent - messenger on the rest running it: sent **Transitions** - 2026-10-10 14:14 (new) → proposed (announced): novox/mesh-catalog#182's head announced - 2026-10-10 14:15 proposed → checked (checked): the verdict names this commit - 2026-10-10 14:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 14:18 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 14:18 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-10 14: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`.
Author
Contributor

Merge check at cd851049

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

  • tier 0: desk-channel, messenger
  • novox: receives desk-channel, messenger
  • read by no module's build: modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md, modules/messenger/cmd/messenger/restart_test.go

Run by the build seat on ace as build-1791640988536996065 (builds --log build-1791640988536996065).

--- the gate: desk-channel, messenger
desk-channel: ok, 1 tool(s), invokes seat:node-notifier.send, keeps state shown; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
messenger: ok, 6 tool(s), invokes seat:mesh-controller.conditions, seat:mesh-controller.root-free, keeps state open, sent, asks, identities; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T13:56:57Z 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-10T13:56:57Z

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 2 module(s) in 1 tier(s): desk-channel, messenger

notes:
  - modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md and modules/messenger/cmd/messenger/restart_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.002s
words: 12 retired words and 70 daemons' lines, none in the 37555 strings of 638 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.011s
agent-home: no archive and no file written into under the agent's home
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/desk-channel
ok  	deskchannel/cmd/desk-channel	1.013s
testing modules/messenger
ok  	messenger/cmd/messenger	1.761s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `cd851049` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: desk-channel, messenger) - `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 desk-channel, messenger → novox; no bus step - tier 0: desk-channel, messenger - novox: receives desk-channel, messenger - read by no module's build: modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md, modules/messenger/cmd/messenger/restart_test.go Run by the build seat on ace as `build-1791640988536996065` (`builds --log build-1791640988536996065`). ``` --- the gate: desk-channel, messenger desk-channel: ok, 1 tool(s), invokes seat:node-notifier.send, keeps state shown; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339) messenger: ok, 6 tool(s), invokes seat:mesh-controller.conditions, seat:mesh-controller.root-free, keeps state open, sent, asks, identities; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T13:56:57Z 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-10T13:56:57Z 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 2 module(s) in 1 tier(s): desk-channel, messenger notes: - modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md and modules/messenger/cmd/messenger/restart_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.002s words: 12 retired words and 70 daemons' lines, none in the 37555 strings of 638 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s agent-home: no archive and no file written into under the agent's home 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/desk-channel ok deskchannel/cmd/desk-channel 1.013s testing modules/messenger ok messenger/cmd/messenger 1.761s --- its merge-check-typescript.sh (typescript toolchain) ```
jschoubben added 1 commit 2026-10-10 14:13:59 +00:00
Review: keep the desk's notification ids so lost answers are said again in place (issue 384)
mesh/merge-gate pass: builds desk-channel, messenger → novox; 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
45361b013a
dunst.started says the notifier's bundle started again: the notifications stay on screen and only the
answers they waited for are lost. Forgetting their ids made the router's message a second popup beside a
dead one. The desk now keeps the ids and says answers-lost-at; the router's message replaces each
notification in place.

Whether a message is said again is now its own (last said before the answers were lost), so a router
that started after the loss still says it and a repeated standing says nothing. It is sent to the desk
directly, not through the outbox, whose failure path moves a warning to Telegram; a failed send is tried
again at the next standing.
Author
Contributor

Merge check at 45361b01

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

  • tier 0: desk-channel, messenger
  • novox: receives desk-channel, messenger
  • read by no module's build: modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md, modules/messenger/cmd/messenger/restart_test.go

Run by the build seat on ace as build-1791641658729933265 (builds --log build-1791641658729933265).

--- the gate: desk-channel, messenger
desk-channel: ok, 1 tool(s), invokes seat:node-notifier.send, keeps state shown; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
messenger: ok, 6 tool(s), invokes seat:mesh-controller.conditions, seat:mesh-controller.root-free, keeps state open, sent, asks, identities; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T14:06:57Z 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-10T14:06:57Z

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 2 module(s) in 1 tier(s): desk-channel, messenger

notes:
  - modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md and modules/messenger/cmd/messenger/restart_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 37552 strings of 638 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.010s
agent-home: no archive and no file written into under the agent's home
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: 70, as kept
testing modules/desk-channel
ok  	deskchannel/cmd/desk-channel	1.012s
testing modules/messenger
ok  	messenger/cmd/messenger	1.781s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `45361b01` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: desk-channel, messenger) - `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 desk-channel, messenger → novox; no bus step - tier 0: desk-channel, messenger - novox: receives desk-channel, messenger - read by no module's build: modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md, modules/messenger/cmd/messenger/restart_test.go Run by the build seat on ace as `build-1791641658729933265` (`builds --log build-1791641658729933265`). ``` --- the gate: desk-channel, messenger desk-channel: ok, 1 tool(s), invokes seat:node-notifier.send, keeps state shown; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339) messenger: ok, 6 tool(s), invokes seat:mesh-controller.conditions, seat:mesh-controller.root-free, keeps state open, sent, asks, identities; WARNING: settings ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T14:06:57Z 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-10T14:06:57Z 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 2 module(s) in 1 tier(s): desk-channel, messenger notes: - modules/desk-channel/README.md, modules/desk-channel/cmd/desk-channel/desk_test.go, modules/messenger/README.md and modules/messenger/cmd/messenger/restart_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 37552 strings of 638 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s agent-home: no archive and no file written into under the agent's home 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: 70, as kept testing modules/desk-channel ok deskchannel/cmd/desk-channel 1.012s testing modules/messenger ok messenger/cmd/messenger 1.781s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit fb77be42ca into main 2026-10-10 14:17:04 +00:00
mesh-admin deleted branch fix/issue-384-restart-replays-nothing 2026-10-10 14:17:05 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#182