mesh-tools

4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e9009b7f04	Answer mesh/state.info with a bucket's fill and caps, so a bundle's tools can say how full its state is (issue 1952)	2026-10-29 22:43:58 +01:00
jschoubben	1583fa85d9	Let a bundle write a state key with its own time to live and hear its end, so wakes need no in-process timer (issue 1952) mesh/state.create and mesh/state.put take ttl_seconds (mesh-sdk 32f5ce3's CreateTTL/RenewTTL contract); a bucket not declared key-ttl is refused, naming it; a watch hands an expired key as op "expire". Pins mesh-sdk 32f5ce3.	2026-10-29 22:11:39 +01:00
jochen	d0128adf5b	Fail the contention test when the two writers never collided: it would prove nothing (the review of 2026-10-10) mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of … Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery delivered Details mesh/delivery-group group feat/a-counter-by-compare-and-set merged: every member is merged Details	2026-10-10 12:33:43 +02:00
jochen	1eaa1abbe9	Prove a write by compare-and-set loses no update under contention, on a real bus (hq research 042) mesh/delivery-group group feat/a-counter-by-compare-and-set checking: 0 of 2 member(s) ready Details mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of … Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery superseded: a newer head of the same pull request Details The issues module will hand out numbers through mesh/state.create and update. Two writers incrementing one counter a thousand times each through the module's bus now end at two thousand with every number handed out once; a stale, zero or future revision is refused with the lost-write code and writes nothing; a deleted key can be created again; and the lost-write code reaches a bundle wrapped or not, and no other refusal carries it. Both runtime tests run in the check's bundleless list, so mesh/repo-check runs them. Part of the issue tracker decision, hq research 042.	2026-10-10 12:31:06 +02:00