Repository navigation
fix: retain ready runner during brief claim contention - #152
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 24, 2026 11:52
10 of 13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A readiness heartbeat can briefly lock the only ready Runner. The reservation uses
SKIP LOCKED, so it previously took the cold path immediately even though the standby remained eligible. This also makes a prepared hosted recovery drill miss its intended Runner.Retry an empty reservation up to four times, 50 ms apart, only while a fresh candidate remains visible in the same source-bound pool. Successful reservations, assignment callbacks, database errors and ambiguous outcomes are never replayed. Missing, stale, assigned or persistently locked reserves retain the cold fallback. Public English/German execution documentation describes the bound.
Validation:
npm run check: build/typecheck/lint and 1,060 tests pass; 74 existing optional tests skipped in that command (targeted database checks run separately). Existing lint warnings remain.Refs #95. The hosted interruption and subsequent recovery remain unqualified; the observed live fallback is consistent with contention, but its transient lock was not captured. No customer Apply or state modification is part of this PR.