Skip to content

fix: guard scheduler daemon ownership and bound test waits - #513

Merged
scode merged 1 commit into
mainfrom
pr/scheduler-daemon-ownership
Nov 8, 2026
Merged

scode merged 1 commit into
mainfrom
pr/scheduler-daemon-ownership

Conversation

@scode

@scode scode commented Nov 8, 2026

Copy link
Copy Markdown
Owner

The daemon lifecycle test waited without a deadline while checking duplicate
startup and shutdown, so CI could hang without identifying the stuck phase.

Heartbeat reads cannot arbitrate ownership: an in-place write can look like an
absent daemon, and two starters can both observe no owner. A lifetime lock is
needed even when the heartbeat is missing or stale.

The daemon lifecycle test waited without a deadline while checking duplicate
startup and shutdown, so CI could hang without identifying the stuck phase.

Heartbeat reads cannot arbitrate ownership: an in-place write can look like an
absent daemon, and two starters can both observe no owner. A lifetime lock is
needed even when the heartbeat is missing or stale.
@scode
scode marked this pull request as ready for review November 8, 2026 00:16
@scode
scode merged commit 915e041 into main Nov 8, 2026
5 checks passed
@scode
scode deleted the pr/scheduler-daemon-ownership branch November 8, 2026 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant