mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-09-22 08:02:24 +00:00
l0ng-ai
a077d47051
`reap_stranded_clears_a_seat_holder_with_no_pidfile` failed on macOS CI often enough to red a PR that touched nothing near it: after a confirmed reap the lock file still named the dead holder. A seat is not free the same instant its holder is confirmed dead. The kernel releases the lock while tearing the process down, and any descriptor a `fork` left behind holds it a moment longer — BSD `flock` counts an inherited descriptor as another reference to the one lock rather than a second lock, which this module already records on the claim side (`a_reference_a_forking_neighbour_left_behind_does_not_lose_the_seat`, and the retry loop `claim_within` exists for). `clear_record_if_free` had no such patience: one `EWOULDBLOCK` ended the attempt, and nothing ever revisits the file, so the dead pid stayed in it for good — where a later pre-recording build holding the seat would make that number, by then possibly reused, read as the holder. It now retries for 500ms. The rule it enforces is unchanged: the record is truncated only while the kernel says the seat is free, so a live holder that outlasts the grace still keeps its record. The guard was measured both ways — with the grace at zero `clearing_the_record_waits_out_a_seat_that_is_about_to_come_back` fails with exactly the assertion CI reported. Claude-Session: https://claude.ai/code/session_01Mnerr8RZ23Nd4cxyfeqxiu