You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6fce5ec
Browse filesBrowse the repository at this point in the historyBrowse files
fix(daemon): let a retained close answer every later stop of its instance
A close that keeps its registration left the state dir claimed with no
record of why, and the record it did write stopped answering after 60 s.
A stop that arrived later found a claimed dir, a closed listener, and no
evidence: it sat out its whole budget and failed with an unconfirmed
shutdown at a runtime that had already stopped serving.
- Every close that leaves the registration in place publishes its
retention record, whether or not a stop asked for it. The ledger answers
a request; this is a fact about the state dir, owed to whoever reads it
next. `finish()` states it for the case where the removal itself failed.
- A `retained` record answers by lifetime, not by age: the state it reports
holds until a new acquisition clears the file, so the age bound added
nothing beyond the pid and start-time fence. A `released` record keeps
its window, because its job is to answer the stop that asked.
- The wait proves the instance is still the process the record names
before trusting an aged record. A dead host's leftover file is not a
registration someone holds, and its honest answer is that nothing runs.
- Only a runtime a host owns publishes these records. A detached daemon's
stop signals its process and reads the shutdown report, so a completion
record there would state a fact nobody reads.
Co-Authored-By: Claude <[email protected]>
0 commit comments