mesh-vault: own answers a node within its bound — assignments from a watched mirror, one read per module, one synced record per answer (issue 1126) #545

Merged

mesh-tools merged 2 commits from fix/1126-vault-own into main 2026-10-28 14:20:36 +00:00

Conversation 1 Commits 2 Files Changed 7

+347 -29

2 Commits

Author	SHA1	Message	Date
jschoubben	a9d96b30be	mesh-vault: a watch of the assignments begun again keeps nothing an earlier attempt took, and a module the mirror lacks is read directly before a credential is refused (issue 1126, review round 1) ... A watch that failed partway kept what it had taken; begun again, the runtime does not hand a key deleted meanwhile, so a removed assignment read as standing and credentialRefusal could hand a consumer credential to a node no longer running its module. Each attempt now begins from nothing held, and a late delivery to an older attempt changes nothing. A 'not on the node' refusal is confirmed by a direct read first, since a watched mirror can be behind.	2026-10-28 14:55:36 +01:00
jschoubben	277a4d0060	mesh-vault answers own in one pass: assignments from its watch, each module's once, one synced record per answer (issue 1126) ... Seed-9's probe (13:31-13:36Z): novox's own of 57 secrets and 146 credentials took 26 s, past the node-engine's 15 s, and ace and novox refused their whole shadow answer. own read the controller's assignment over the bus once per secret and per credential (203 reads), read every record of every node, and synced the hand-out record once per value, under the one lock every node's answers share. Now the vault watches the assignments mirror (a watch, never a poll) and reads it from memory once caught up, over the bus until then; one answer reads each module's assignment once; only own/<node>/ records are read; and every hand-out of one answer is recorded in one synced write, none handed when it cannot be. Quick fix weighed: a longer bound in the node-engine (VaultWithin). Thorough fix chosen: the cost grows with every module and every node, and the lock is shared by every shadow answer and every apply.	2026-10-28 14:47:20 +01:00