The delivery view forgets a write or event the bus refused, so 'on the machines' is not left stale (issue 1126) #97

Merged

mesh-tools merged 1 commits from fix/1126-reach-now into main 2026-10-28 15:18:55 +00:00

Conversation 1 Commits 1 Files Changed 5

+140 -41

1 Commits

Author	SHA1	Message	Date
jschoubben	726bbf1f1f	The view writes a reach or says an event again when the bus refused it, so a refused write never leaves the reach state at an older have (issue 1126) ... The view remembered a reach value, a reached head and a motion event as written or said before the bus took them; a write refused at its start (no responders) was never made again while the derivation stayed the same, and mesh-delivery.show said mesh-delivery-view not running on shanks while node_haves said it running. Quick fix: forget only the refused reach write. Thorough fix, chosen: every write and event the view makes after its lock (reach, reached head, delivered revision, motion) answers its error, and the model forgets what was refused, so the next change it takes in makes it again; one place, the writer of the state both mesh-delivery.show and knowledge-base.progress read.	2026-10-28 16:11:52 +01:00