4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	316a5a2fc3	A watch given up or stopped hands over nothing more; arrival of current values restarts its bound (issue 774) ... Quick: check the watch context before each deliver in StateWatch. Thorough (chosen, same file kind): also LogWatch drops a message fetched as it stopped, and the bound restarts on arrival, not only after the bundle took a value.	2026-10-30 18:22:01 +01:00
jschoubben	ac645e2cae	Refuse a held-back membership's old wrapper in the tool runner, pinning mesh-sdk's review-round-1 codec ... The old grants part wrote its wrapper for a held-back membership too; the new part leaves such a key alone, and taking it would serve what the hold kept back with the stream's copy ignored. The integration test now proves that copy is served instead. Review round 1 of issue 774's fix.	2026-10-30 15:38:40 +01:00
jschoubben	a479a90fb2	Read the grants part's memberships through mesh-sdk's codec, so the tool runner serves its node's modules ... The tool runner unmarshalled the state's value straight into its membership; the grants part had written its wrapper there, so every module decoded empty, was marked as given by the grants part, and the correct copy on the assignments stream was passed over: novox served no tool. followGrants now reads with membership.BareGrantsMembership, which takes the bare membership, still takes the old wrapper (what the live mesh holds until the part writes again), and refuses a value naming no node or module, leaving the stream's copy in force. The fixture IssueInGrants built its value by hand from this package's type and so agreed with the mistake; it now writes through mesh-sdk's encoder, and IssueInGrantsWrapped writes the old wrapper for one integration test that proves tools and state are served from it (it fails without this fix with the empty membership seen live). Issue 774 (the bus login list, L3). Quick fix: unwrap here alone. Thorough, chosen: one codec in mesh-sdk the writer and this reader share, so the two cannot drift again. Pins mesh-sdk at the head of its fix/memberships-shape.	2026-10-30 15:31:26 +01:00
jschoubben	0211844e6a	Bound a state watch's hand-over by its progress, not its whole set, so a large state's newest keys are handed over (issue 1726) ... The gitea module's watch of mesh-delivery-checker.owed failed at every attempt since 03:05 on novox: about 200 owed keys, each a round trip to the bundle, outlast a 10 s bound for the whole set. The bundle dropped its handler, the oldest keys were written again every 40 s and the newest, handed over last, never were: group fix/1937-done-key-blobs's pass never reached mesh/check. StateWatch now fails only when no current value is handed over within StateTimeout.	2026-10-24 07:42:08 +02:00