A waiting ask hears its step's end even when its own watch goes deaf (four lost checks, 2026-10-28) #121

Merged

mesh-tools merged 2 commits from fix/lost-check into main 2026-10-28 20:40:58 +00:00

Conversation 1 Commits 2 Files Changed 2

+284

2 Commits

Author	SHA1	Message	Date
jschoubben	f91340fe82	buildrun: open a steps watch again that closed having heard nothing, up to 3 closes in a row ... A watch that closed at once was left for good, so an ask whose own watch went deaf was read only at a reconnect (review of fix/lost-check).	2026-10-28 20:35:02 +01:00
jschoubben	6aeb401095	buildrun: read an ask's step at every step end of its build module, so a deaf watch loses no end ... mesh-catalog #553's verdict stayed running after its step passed on shanks at 19:09:31Z on 2026-10-28: the watch of that one step key, opened at 18:46:05Z, heard neither the start nor the end and never closed. HeardEnds stands between Asker and each ask's watch: nudged at each step end of the same build module (HearEnds: one watch per steps state) and at a reconnect, every waited ask reads its keys now; a watch that closes is opened again, at most 3 times. The checker and the builder both wait through it. Tests: a section of the asker's test (deaf, nudged by another module and by its own, a watch that closes); counts unchanged.	2026-10-28 20:29:30 +01:00