5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	2c37f48f9d	A source revision is delivered over the nodes present: the view leaves out a node the watchman says is away and names it, and the node counts once it runs its wants (ADR 0603 §7)	2026-11-03 17:16:30 +01:00
jschoubben	6bc16d74db	Write and take in a merge that leaves no module.json, so a module-less repository's reach is not held for ever and a removed last module is dropped (issue 1126) ... The forge bridge wrote no merged message for such a merge, so taken.<repo> never moved and the view held 'the indexer has not yet taken in <head>' (hq #490-#492). The bridge now writes it with no trees; the indexer drops every module of the repository on it, after the same order check as any merged message. The view needed no change: with the taken key moving it reaches the merge, which its new row proves. Needs mesh-sdk fix/1126-no-module-reach (a merged message may carry no trees).	2026-11-03 16:45:06 +01:00
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
jschoubben	afd5a3ba07	A module a node wants and runs nothing countable of holds no head back; the reached head's event names its merges as not yet on the machines; pin mesh-sdk e44cbaf (review of issue 1280, ADR 0556 clause 2)	2026-10-26 21:15:31 +01:00
jschoubben	f907be2c14	The view derives per repository up to which merge every node runs it, keeps it as its state reach and says each reached head, so a fix on the machines reads delivered (issue 1280, ADR 0556 clauses 2 and 3)	2026-10-26 20:56:12 +01:00