5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	cf930388f9	The standing test's runs last 0.6 of failingAfterMs of clock as well as two attempts, so a success that does not reset a run is caught; the addition test holds a thousand stable passes, so 'first pass' is proved (review of the standing test races)	2026-10-26 21:49:03 +01:00
jschoubben	36ae0c691b	The standing and retirement tests wait on what they mean, not on a slept fraction of a bound: announcements are timed from the clock at the moment they are said, short runs are counted in attempts, an addition is proved by a hold it must not wait for (the second timing race of one kind in a day; issue 1126)	2026-10-26 21:44:06 +01:00
jschoubben	3a095a66be	The standing test keeps c failing alone after its ask is dropped, so its only recovery is its retirement: clearing every failure at once raced the loop's read of the new list under load (issue 1126; the hidden failure of try-1793042418286545971, issue 1901)	2026-10-26 21:33:20 +01:00
mesh-tools	1bc5719b8b	Feature 57 (config and provisioning): release mesh-sdk, the reviewed release branch on top of main	2026-10-16 08:24:11 +00:00
jochen	d49d3a14d8	0.1.14: the provider loop says a consumer it keeps failing on the bus, and its recovery (hq ADR 0224, issue 272) ... No provider on runProvisioner passed announce, and the loop had no standing per consumer, so the object store, the SQL and document stores, the mail server and the others failed their consumers in their journals alone. The loop now keeps the Go copy's standing (failing after five minutes, again every fifteen, recovered on success, when unasked or retired, and on the first success since start) and says it through the SDK's emit unless given another announce.	2026-10-13 08:26:33 +02:00