A build step names the process that runs it, so a restarted build module clears what a gone process left running (issue 1890) #105

Merged

mesh-tools merged 2 commits from fix/1890-step-owner into main 2026-10-27 07:19:36 +00:00

Conversation 2 Commits 2 Files Changed 9

+419 -58

2 Commits

Author	SHA1	Message	Date
jochen	db1007ffdd	Delete a gone process's ask key instead of ending it, so its redelivery still answers the asker (issue 1890) ... ADR 0525 §6 has the stream redeliver an ask whose node stopped, and the asker takes the first end it reads: ending the key at a restart failed checks a redelivery would still run. The sweep now deletes such a key, guarded by the revision read, so the asker keeps waiting and the stale key leaves the counts of what runs; a hand-started step of a gone owner is still ended at once. A missing boot id is said once at start.	2026-10-27 01:29:48 +01:00
jochen	981a35b598	End a step left by a previous process at once: every step names its owner (issue 1890) ... A delivery that replaced mesh-build-go left a check ask's key running, and the new process's start sweep spared it as an ask younger than the step bound, so it held a build slot until a hand end (issue 1890, note 21). Each step now records its owner (boot id, pid, process start); the sweep ends a running step of another owner at once and says its owner, while a key with no owner keeps the earlier rule. The conformance kit gains the left-running case every build module runs through its own start sweep.	2026-10-27 01:19:29 +01:00