The node's shadow says which input woke each answer (issue 1126) #163

2026-10-28T13:58:50Z

mesh-tools commented

2026-10-28 13:58:50 +00:00

Issue 1126 note 78. In the seed-9 probe, shanks answered one candidate four times while a node-engine delivery moved its inputs. The log line 'answering placement candidate … (revision N)' did not say why, so the probe's safety rule could not tell a loop from moving inputs.

The line now reads '… (revision N; woken by X)', where X is the first answer, a retry after an unanswered read, the candidate, or the inputs that changed (placement, records, modules, values, haves, wants). The single change counter is now one counter per input; it decides when to answer again exactly as before (reviewed: every count only rises, so the sum is equal exactly when each count is equal).

Tests: four rows in TestTheNodeComposesItsWantsFromTheBus, failing first; unit count unchanged. TestNatsANodeThePlacementNamesComposesAndAppliesItsOwn passes (25.8 s).
Not a group: mesh-catalog (mesh-vault own) is independent.

Reviewed-by: rev-vault-own@shanks at 8bd0b5db15

Issue 1126 note 78. In the seed-9 probe, shanks answered one candidate four times while a node-engine delivery moved its inputs. The log line 'answering placement candidate … (revision N)' did not say why, so the probe's safety rule could not tell a loop from moving inputs. The line now reads '… (revision N; woken by X)', where X is the first answer, a retry after an unanswered read, the candidate, or the inputs that changed (placement, records, modules, values, haves, wants). The single change counter is now one counter per input; it decides when to answer again exactly as before (reviewed: every count only rises, so the sum is equal exactly when each count is equal). Tests: four rows in TestTheNodeComposesItsWantsFromTheBus, failing first; unit count unchanged. TestNatsANodeThePlacementNamesComposesAndAppliesItsOwn passes (25.8 s). Not a group: mesh-catalog (mesh-vault own) is independent. Reviewed-by: rev-vault-own@shanks at 8bd0b5db15a34aa881e7f16a95e73e523faf1995

mesh-tools added 1 commit 2026-10-28 13:58:50 +00:00

Say which input woke each placement candidate's answer, so a probe's safety check tells a loop from moving inputs (issue 1126)

mesh/delivery merged: source.main moved to novox/mesh-host@690aa662a837

Details

mesh/delivery-group group fix/1126-vault-own merged: every member is merged

Details

mesh/check pass 8bd0b5db15a3 on b4fd2cc210bf | unit 1639 run, 4201 kept, 46 skipped | integration 1674 run, 4215 kept, 47 skipped | over bound: unit, …

8bd0b5db15

Each answer's line now reads 'answering placement candidate G (revision N; woken by X)', X being its first answer,
a retry after a read the bus did not answer, the candidate, or the inputs that changed (placement, records, modules,
values, haves, wants). The single input counter becomes one per input, which also decides whether a group is answered
again, as before.

Quick fix weighed: a counter word in the line. Thorough fix chosen: one count per input, so the line names exactly what
moved since the group's last answer.

mesh-tools commented

2026-10-28 13:58:53 +00:00

Delivery novox/mesh-host@8bd0b5db15a3 — merged since 2026-10-28T14:20:40Z

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

Group fix/1126-vault-own: novox/mesh-catalog@a9d96b30be, novox/mesh-host@8bd0b5db15

composed together: pass — the checker's verdict at the members' heads (e56c5fb70f60)

Transitions

2026-10-28 13:58 (new) → proposed (announced): novox/mesh-host#163's head announced
2026-10-28 13:58 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-10-28 14:20 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-host@8bd0b5db15a3` — **merged** since 2026-10-28T14:20:40Z **Source** — source.main moved to novox/mesh-host@690aa662a837. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/1126-vault-own`: novox/mesh-catalog@a9d96b30be8d, novox/mesh-host@8bd0b5db15a3 - composed together: pass — the checker's verdict at the members' heads (e56c5fb70f60) **Transitions** - 2026-10-28 13:58 (new) → proposed (announced): novox/mesh-host#163's head announced - 2026-10-28 13:58 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-10-28 14:20 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 690aa662a8 into main

2026-10-28 14:20:39 +00:00

mesh-tools deleted branch fix/1126-vault-own

2026-10-28 14:20:39 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#163