An answered ask is kept until its yes is in the want, and an ask taken away is asked again under a new asking (issue 1966) #195

2026-11-09T22:00:14Z

mesh-tools commented

2026-11-09 22:00:14 +00:00

The operator's yes for nats on novox (2026-11-09 10:32 UTC) was never counted: the assigner's staleAsks took the ask away in the same second, and answeredWith counts a yes only while its ask is at its key. The ask for the next composition was taken away after each assigner restart and written again under asking 0, an id the router had ended, so the teller returned silently and never asked again.

Assigner: record and restore asks are numbered by the time they are written (as hold asks were); a record ask is kept while its node's have waits on it, while the have is mid-move, and while its yes is given but not yet in the want; staleAsk judges the module's own digest, not the node-wide one; the journal says why an ask is taken away. Teller: a key written again under an id the router kept is said, and asked again under a new asking.

Not built (noted on issue 1966): a read tool for the history of a module's have phases; the same rule for hold and restore staleness.

issue 1966

Reviewed-by: review-1966@shanks at 8596b9abf5
Pushed-by: lead-47@shanks

https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

The operator's yes for nats on novox (2026-11-09 10:32 UTC) was never counted: the assigner's staleAsks took the ask away in the same second, and answeredWith counts a yes only while its ask is at its key. The ask for the next composition was taken away after each assigner restart and written again under asking 0, an id the router had ended, so the teller returned silently and never asked again. Assigner: record and restore asks are numbered by the time they are written (as hold asks were); a record ask is kept while its node's have waits on it, while the have is mid-move, and while its yes is given but not yet in the want; staleAsk judges the module's own digest, not the node-wide one; the journal says why an ask is taken away. Teller: a key written again under an id the router kept is said, and asked again under a new asking. Not built (noted on issue 1966): a read tool for the history of a module's have phases; the same rule for hold and restore staleness. issue 1966 Reviewed-by: review-1966@shanks at 8596b9abf52cf0c6f883678e3a842b257c01d6c0 Pushed-by: lead-47@shanks https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

mesh-tools added 3 commits 2026-11-09 22:00:14 +00:00

Subtask A: a record ask is kept while its node waits on it or its yes is unwritten, and an ask written again is asked again under a new id (issue 1966) 2469531c2f

The assigner took record.novox.nats away as stale in the same second the operator's yes
was written (the yes counts only while the ask is there), and rewrote it under the id the
router already kept, so the teller never asked it again. The stale test compared a module's
ask with the whole node's composition; it now reads the module's own have, and restore and
record asks are numbered by their writing's time as hold asks are.

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

Subtask B: the teller says an assigner ask written again under the id the router kept is not asked, with a row per kind that a new asking is asked again (issue 1966) 5ab0d8ca88

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

Subtask C: the two new tests of issue 1966 run inside existing test functions, to stay within the test budget

mesh/delivery merged: source.main moved to novox/mesh-delivery@10066c5ec0c0

Details

mesh/check checking 8596b9abf52c on 10066c5ec0c0

8596b9abf5

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

mesh-tools commented

2026-11-09 22:00:18 +00:00

Delivery novox/mesh-delivery@8596b9abf52c — merged since 2026-11-09T22:08:41Z

Source — source.main moved to novox/mesh-delivery@10066c5ec0. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-09 22:00 (new) → proposed (announced): novox/mesh-delivery#195's head announced
2026-11-09 22:00 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-09 22:08 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-delivery@8596b9abf52c` — **merged** since 2026-11-09T22:08:41Z **Source** — source.main moved to novox/mesh-delivery@10066c5ec0c0. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-09 22:00 (new) → proposed (announced): novox/mesh-delivery#195's head announced - 2026-11-09 22:00 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-09 22:08 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 10066c5ec0 into main

2026-11-09 22:08:39 +00:00

mesh-tools deleted branch fix/1966-record-ask-lost

2026-11-09 22:08:40 +00:00

mesh-tools referenced this pull request

2026-11-10 00:39:37 +00:00

An assigner ask that ends at the channel without an answer is asked again under a new asking (issue 1966) #198

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#195