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 5ac0baf
Browse filesBrowse the repository at this point in the historyBrowse files
fix(daemon): take the owner identity from host-kit and refuse unproven records
Address review on #3102. The daemon asserted its own ownership identity with a
second copy of the host-kit constructor, so the daemon.json fence and the
device-claim fence could drift apart; it now calls readCurrentOwnerIdentity()
like every other ownership fence does.
That exposed a weaker rule than the issue needs: two records that both failed to
read a start time agreed on nothing, and agreeing on nothing was reported as a
match — the pid-only fallback the fence exists to refuse. Ownership now returns a
third verdict, unproven, for a record that matches on pid and can be proved
neither way. removeInfoOwnedBy declines it, because leaving a record a dead pid
left behind costs a client one liveness probe while deleting a successor's
metadata is unrecoverable; the loss watch declines it too, since nothing proves a
takeover happened. Reporting it as `replaced` would announce an event with no
evidence of one.
Also from review: the startup-failure exit now tears the loss watch down before
touching daemon.json, so a failed runtime cannot report a loss for a record it
just removed itself; the watch stops when the state dir is pruned rather than
polling a directory that no longer exists; the state `decodable` is renamed
`ownerless`, because it names the record that has no owner rather than the one
that fails to decode; and the dead readProcessStartTime re-export is gone.
0 commit comments