One message per problem: a reminder replaces, a blip says nothing (issues 373 and 369) #176

Merged
mesh-admin merged 3 commits from fix/373-one-message-per-condition into main 2026-10-10 12:39:07 +00:00
Contributor

Fixes the router's and the channels' part of issues 373 and 369 (the operator no longer trusts the notifications: duplicates, stale and repeated warnings). The controller's part (a refusal repeated for eleven hours) is mesh-controller fix/373-one-message-per-condition.

Causes found

  • A reminder or escalation was a new message beside the first. sendEntries always called Send with a fresh handle and kept only the first message's id, so "Now urgent" and "Still open" stood beside the original on the desk (critical urgency never times out) and on Telegram. The reminder rule counted from the first send, so a reminder followed an escalation 31 s later (seen 12:57:49 / 12:58:20).
  • A question's end never reached the reminder. showClosed edits the record's first message; a reminder carrying the ask's buttons was a different message, so its buttons stayed.
  • "If nobody answers by 23:33" was a week-long ask's expiry said as a clock time alone (it expired 16 Oct 23:33, not that night).
  • A flapping unit was said at every apply. cleared edited the message at once ("Resolved") and the reopen 15 s later edited it again ("again, Nth time"); on the desk an edit is replace_id of a notification already gone, so each one popped up again.

Fix

  • messenger: a record said again where its message is shown (reminder, escalation, quiet reminder) goes alone and replaces that message (Replace = send/show under the existing handle). A problem first said in a digest gets its own message next time; later words replace or edit that one. A reminder counts from when it was last said. A clearing is said once it stays cleared 2 min (10 min once it has come back); raised again before, the message continues without a word. Cleared before it was ever said and back: said (never swallowed). An ask's expiry says its day when not today.
  • desk-channel: a send/show under a handle already shown replaces its notification on each machine by the notifier's replace_id; anew only on machines it was not on. Edits unchanged.
  • telegram: the same deletes the earlier message and sends the new one (ringing as its kind rings; an edit there is silent); one the service will not delete loses its buttons and says a newer message follows.
  • Issue 371's Details tests adapted: the three messages are now one sent and two said in its place; each keeps its own Details.

Tests (mutation-checked: each fix removed fails a test)

  • onemessage_test.go: a unit flapping 22 times at 15 s plus a slower flap is said once, its clearing once when it stops; a new problem meanwhile is said; an urgent blip rings once; cleared-before-said-and-back is said; a digest-said problem gets its own message; an ended question leaves no message with its answers; expiry with its day.
  • holder_test.go: reminder and escalation replace (Replace with the first message's id); no reminder within the hour after an escalation.
  • desk: TestAMessageSaidAgainUnderItsHandleReplacesItsNotification checks the notify call's replace_id per machine.
  • telegram: TestAMessageSaidAgainUnderItsHandleReplacesTheEarlierOne (deleteMessage of the earlier id, ringing send, fallback edit without buttons).

MESH_CHECK_MODULES=messenger,desk-channel,telegram sh merge-check.sh passes locally.

Acceptance: one notification per problem at any time, updated in place; no "again, Nth time" for a flapping unit; nothing ended still offering buttons.

Not merged: needs one independent review.

Reviewers' checklist: a genuinely new problem is never swallowed by the dedup; an urgent condition still rings once; a cleared-and-really-gone condition is said once; no condition is lost when a message is replaced; tests fail with the fixes removed.

Fixes the router's and the channels' part of issues 373 and 369 (the operator no longer trusts the notifications: duplicates, stale and repeated warnings). The controller's part (a refusal repeated for eleven hours) is mesh-controller `fix/373-one-message-per-condition`. ## Causes found - **A reminder or escalation was a new message beside the first.** `sendEntries` always called `Send` with a fresh handle and kept only the *first* message's id, so "Now urgent" and "Still open" stood beside the original on the desk (critical urgency never times out) and on Telegram. The reminder rule counted from the first send, so a reminder followed an escalation 31 s later (seen 12:57:49 / 12:58:20). - **A question's end never reached the reminder.** `showClosed` edits the record's first message; a reminder carrying the ask's buttons was a different message, so its buttons stayed. - **"If nobody answers by 23:33"** was a week-long ask's expiry said as a clock time alone (it expired 16 Oct 23:33, not that night). - **A flapping unit was said at every apply.** `cleared` edited the message at once ("Resolved") and the reopen 15 s later edited it again ("again, Nth time"); on the desk an edit is `replace_id` of a notification already gone, so each one popped up again. ## Fix - **messenger**: a record said again where its message is shown (reminder, escalation, quiet reminder) goes alone and **replaces** that message (`Replace` = `send`/`show` under the existing handle). A problem first said in a digest gets its own message next time; later words replace or edit that one. A reminder counts from when it was **last** said. A clearing is said once it **stays cleared 2 min** (10 min once it has come back); raised again before, the message continues without a word. Cleared before it was ever said and back: said (never swallowed). An ask's expiry says its day when not today. - **desk-channel**: a `send`/`show` under a handle already shown replaces its notification on each machine by the notifier's `replace_id`; anew only on machines it was not on. Edits unchanged. - **telegram**: the same deletes the earlier message and sends the new one (ringing as its kind rings; an edit there is silent); one the service will not delete loses its buttons and says a newer message follows. - Issue 371's Details tests adapted: the three messages are now one sent and two said in its place; each keeps its own Details. ## Tests (mutation-checked: each fix removed fails a test) - `onemessage_test.go`: a unit flapping 22 times at 15 s plus a slower flap is said **once**, its clearing once when it stops; a new problem meanwhile is said; an urgent blip rings once; cleared-before-said-and-back is said; a digest-said problem gets its own message; an ended question leaves no message with its answers; expiry with its day. - `holder_test.go`: reminder and escalation replace (`Replace` with the first message's id); no reminder within the hour after an escalation. - desk: `TestAMessageSaidAgainUnderItsHandleReplacesItsNotification` checks the notify call's `replace_id` per machine. - telegram: `TestAMessageSaidAgainUnderItsHandleReplacesTheEarlierOne` (deleteMessage of the earlier id, ringing send, fallback edit without buttons). `MESH_CHECK_MODULES=messenger,desk-channel,telegram sh merge-check.sh` passes locally. **Acceptance:** one notification per problem at any time, updated in place; no "again, Nth time" for a flapping unit; nothing ended still offering buttons. Not merged: needs one independent review. Reviewers' checklist: a genuinely new problem is never swallowed by the dedup; an urgent condition still rings once; a cleared-and-really-gone condition is said once; no condition is lost when a message is replaced; tests fail with the fixes removed.
Author
Contributor

Delivery novox/mesh-catalog@8dfc19c9f7c8 — superseded since 2026-10-10T12:47:10Z

Covered: delivered after its walk was superseded: the walk plan-1791636428394969307, which took its walk plan-1791635975240829940 over, ended done

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

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

Group fix/373-one-message-per-condition: novox/mesh-catalog@8dfc19c9f7, novox/mesh-controller@2e0a7d1cbd

  • composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Machines

  • build-agent on ace: passed — carried by plan-1791637155946612018

Transitions

  • 2026-10-10 12:32 (new) → proposed (announced): novox/mesh-catalog#176's head announced
  • 2026-10-10 12:34 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 12:34 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 12:43 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 12:47 published → superseded (superseded): its walk was superseded and names no walk that took it over: a walk that took it over answers its merge, and it follows that walk (novox/hq ADR 0276)

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@8dfc19c9f7c8` — **superseded** since 2026-10-10T12:47:10Z **Covered**: delivered after its walk was superseded: the walk plan-1791636428394969307, which took its walk plan-1791635975240829940 over, ended done **Delivery plan** — builds desk-channel, messenger, telegram → novox; no bus step - tier 0: desk-channel, messenger, telegram - novox: receives desk-channel, messenger, telegram **Group** `fix/373-one-message-per-condition`: novox/mesh-catalog@8dfc19c9f7c8, novox/mesh-controller@2e0a7d1cbd2d - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - build-agent on ace: passed — carried by plan-1791637155946612018 **Transitions** - 2026-10-10 12:32 (new) → proposed (announced): novox/mesh-catalog#176's head announced - 2026-10-10 12:34 proposed → checked (checked): the verdict names this commit - 2026-10-10 12:34 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 12:43 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 12:47 published → superseded (superseded): its walk was superseded and names no walk that took it over: a walk that took it over answers its merge, and it follows that walk (novox/hq ADR 0276) The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at 0854538b

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

  • tier 0: desk-channel, messenger, telegram
  • novox: receives desk-channel, messenger, telegram
  • read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go

Run by the build seat on novox as build-1791633801943450520 (builds --log build-1791633801943450520).

--- the gate: desk-channel, messenger, telegram
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)
telegram: ok, 1 tool(s), keeps state offset, messages
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
3 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-10T11:55: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-10T11:55:18Z

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

notes:
  - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go and modules/messenger/cmd/messenger/words_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 37448 strings of 637 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
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.011s
testing modules/messenger
ok  	messenger/cmd/messenger	1.818s
testing modules/telegram
ok  	telegram/cmd/telegram	1.043s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `0854538b` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: desk-channel, messenger, telegram) - `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, telegram → novox; no bus step - tier 0: desk-channel, messenger, telegram - novox: receives desk-channel, messenger, telegram - read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go Run by the build seat on novox as `build-1791633801943450520` (`builds --log build-1791633801943450520`). ``` --- the gate: desk-channel, messenger, telegram 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) telegram: ok, 1 tool(s), keeps state offset, messages long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 3 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-10T11:55: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-10T11:55:18Z 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 3 module(s) in 1 tier(s): desk-channel, messenger, telegram notes: - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go and modules/messenger/cmd/messenger/words_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 37448 strings of 637 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s 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.011s testing modules/messenger ok messenger/cmd/messenger 1.818s testing modules/telegram ok telegram/cmd/telegram 1.043s --- its merge-check-typescript.sh (typescript toolchain) ```
Author
Contributor

Merge check at f8778555

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

  • tier 0: desk-channel, messenger, telegram
  • novox: receives desk-channel, messenger, telegram
  • read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go

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

--- the gate: desk-channel, messenger, telegram
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)
telegram: ok, 1 tool(s), keeps state offset, messages
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
3 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-10T11:55: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-10T11:55:18Z

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

notes:
  - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go and modules/messenger/cmd/messenger/words_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.014s
words: 12 retired words and 70 daemons' lines, none in the 37460 strings of 637 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.004s
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.010s
testing modules/messenger
ok  	messenger/cmd/messenger	2.037s
testing modules/telegram
ok  	telegram/cmd/telegram	1.040s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `f8778555` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: desk-channel, messenger, telegram) - `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, telegram → novox; no bus step - tier 0: desk-channel, messenger, telegram - novox: receives desk-channel, messenger, telegram - read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go Run by the build seat on g14 as `build-1791634474941969496` (`builds --log build-1791634474941969496`). ``` --- the gate: desk-channel, messenger, telegram 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) telegram: ok, 1 tool(s), keeps state offset, messages long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 3 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-10T11:55: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-10T11:55:18Z 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 3 module(s) in 1 tier(s): desk-channel, messenger, telegram notes: - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go and modules/messenger/cmd/messenger/words_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.014s words: 12 retired words and 70 daemons' lines, none in the 37460 strings of 637 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.004s 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.010s testing modules/messenger ok messenger/cmd/messenger 2.037s testing modules/telegram ok telegram/cmd/telegram 1.040s --- its merge-check-typescript.sh (typescript toolchain) ```
jschoubben added 2 commits 2026-10-10 12:23:24 +00:00
The operator stopped believing the mesh's notifications: one problem stood
twice on the desk (a reminder beside the message it followed, an escalation
then a reminder 31 s later), a unit failing again at each apply was said
again 22 times, and a question's buttons outlived it on a reminder the
ask's end never reached.

- messenger: a reminder or escalation is said in place of the problem's
  message (Replace under its handle), alone, never as a digest line; a
  problem first said in a digest gets its own message next time. A
  reminder counts from when it was last said. A clearing is said once it
  stays cleared 2 min (10 min once it came back); back before that, the
  message continues without a word. Cleared before ever said and back:
  said. An ask's expiry is said with its day.
- desk-channel: a send or show under a handle already shown replaces its
  notification by the notifier's replace id.
- telegram: the same deletes the earlier message and sends the new one,
  ringing as its kind rings; one it cannot delete loses its buttons.
Review: a blip swallows no escalation or waiting reminder; replace safely (issue 373)
mesh/delivery-group group fix/373-one-message-per-condition ready: every member ready, and composed together they pass
mesh/merge-gate pass: builds desk-channel, messenger, telegram → novox; no bus step; every machine composes with the change as it did without (4 of 4 compo…
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
f8515219b1
- A comeback before the clearing was said rings when it is urgent now, and
  says the reminder or escalation that was waiting when it cleared.
- Comebacks never said are counted apart, so "again, Nth time" counts only
  what the operator was told; an urgent comeback after a said clearing rings
  again in place of its message.
- telegram sends the new message before deleting the earlier one, so a
  failed send leaves the operator a message.
- desk-channel keeps a machine's notification on record when its replace
  fails, and says a message shown nowhere as failed.
- A store that cannot be read sends a new message instead of holding it.
- Tests for each, and for a reminder in a burst and a clearing the channel
  could not take.
jschoubben force-pushed fix/373-one-message-per-condition from f87785554a to f8515219b1 2026-10-10 12:23:24 +00:00 Compare
Author
Contributor

Merge check at f8515219

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

  • tier 0: desk-channel, messenger, telegram
  • novox: receives desk-channel, messenger, telegram
  • read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go, modules/telegram/README.md, modules/telegram/cmd/telegram/channel_test.go

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

--- the gate: desk-channel, messenger, telegram
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)
telegram: ok, 1 tool(s), keeps state offset, messages
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
3 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-10T11:55: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-10T11:55:18Z

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

notes:
  - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go and modules/messenger/cmd/messenger/words_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 37506 strings of 637 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.009s
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.009s
testing modules/messenger
ok  	messenger/cmd/messenger	1.881s
testing modules/telegram
ok  	telegram/cmd/telegram	1.053s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `f8515219` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: desk-channel, messenger, telegram) - `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, telegram → novox; no bus step - tier 0: desk-channel, messenger, telegram - novox: receives desk-channel, messenger, telegram - read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go, modules/telegram/README.md, modules/telegram/cmd/telegram/channel_test.go Run by the build seat on g14 as `build-1791635025094270566` (`builds --log build-1791635025094270566`). ``` --- the gate: desk-channel, messenger, telegram 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) telegram: ok, 1 tool(s), keeps state offset, messages long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 3 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-10T11:55: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-10T11:55:18Z 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 3 module(s) in 1 tier(s): desk-channel, messenger, telegram notes: - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go and modules/messenger/cmd/messenger/words_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 37506 strings of 637 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s 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.009s testing modules/messenger ok messenger/cmd/messenger 1.881s testing modules/telegram ok telegram/cmd/telegram 1.053s --- its merge-check-typescript.sh (typescript toolchain) ```
jschoubben added 1 commit 2026-10-10 12:32:38 +00:00
A silence is said on the shown message, which then times out (issue 373)
mesh/merge-gate pass: builds desk-channel, messenger, telegram → novox; no bus step; every machine composes with the change as it did without (4 of 4 compo…
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: its walk was superseded and names no walk that took it over: a walk that took it over answers its merge, and it follows that wa…
mesh/delivery-group group fix/373-one-message-per-condition closed: a member was closed before the group merged
8dfc19c9f7
Seen at 14:40: machine.shanks.units was silenced for 7 days with a reason,
and its critical popup stood on the desk as "Still open" while the
router logged nothing. A silence now edits the message where it is shown
to "Silenced until <day>: <headline>" with the reason, no answers and no
urgency, so the desk's popup times out; nothing more is said while it
lasts. When the silence ends and the condition is still open, the message
is edited back to its open words. Resolved while silenced, it is said only
where an edit notifies nobody. The silence is taken from the controller's
event and from the 10-min reading of the open set alike.
Author
Contributor

Merge check at 8dfc19c9

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

  • tier 0: desk-channel, messenger, telegram
  • novox: receives desk-channel, messenger, telegram
  • read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go, modules/telegram/README.md, modules/telegram/cmd/telegram/channel_test.go

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

--- the gate: desk-channel, messenger, telegram
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)
telegram: ok, 1 tool(s), keeps state offset, messages
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
3 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-10T12:28: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-10T12:28:18Z

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

notes:
  - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go, modules/telegram/README.md and modules/telegram/cmd/telegram/channel_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 37522 strings of 637 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.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.746s
testing modules/telegram
ok  	telegram/cmd/telegram	1.050s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `8dfc19c9` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: desk-channel, messenger, telegram) - `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, telegram → novox; no bus step - tier 0: desk-channel, messenger, telegram - novox: receives desk-channel, messenger, telegram - read by no module's build: modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go, modules/telegram/README.md, modules/telegram/cmd/telegram/channel_test.go Run by the build seat on ace as `build-1791635572283063254` (`builds --log build-1791635572283063254`). ``` --- the gate: desk-channel, messenger, telegram 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) telegram: ok, 1 tool(s), keeps state offset, messages long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 3 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-10T12:28: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-10T12:28:18Z 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 3 module(s) in 1 tier(s): desk-channel, messenger, telegram notes: - modules/messenger/README.md, modules/messenger/cmd/messenger/details_test.go, modules/messenger/cmd/messenger/history_test.go, modules/messenger/cmd/messenger/holder_test.go, modules/messenger/cmd/messenger/onemessage_test.go, modules/messenger/cmd/messenger/words_test.go, modules/telegram/README.md and modules/telegram/cmd/telegram/channel_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 37522 strings of 637 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.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.746s testing modules/telegram ok telegram/cmd/telegram 1.050s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit 64feabc6c3 into main 2026-10-10 12:39:07 +00:00
mesh-admin deleted branch fix/373-one-message-per-condition 2026-10-10 12:39:07 +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#176