Files
hermes-agent/hermes_cli
teknium1 7a61f1d247 fix(update): an adopted own-pid claim is refreshed, not kept near expiry
Adopting a killed update's marker verbatim kept its started_at. When that
claim was close to the 20-minute ceiling, the retry's own lock expired
seconds into its run and a second updater could start over the same
checkout: live, a detached `hermes update` acquired the lock 6s after the
retry adopted a claim 3s from expiry.

A marker naming our pid can only be a dead predecessor's (nothing
pre-writes one for `hermes update`, which always runs under a parent's
claim), so it is a new attempt and is claimed fresh like any dead holder's.
Only one acquire runs per process, so this cannot renew a wedged update.
2026-09-23 11:31:37 -07:00
..
…
…
…
…
…
…
…
…