Repository navigation
fix(scheduler): add advisory-lock leader election - #675
Open
woahwhattheheck wants to merge 15 commits into
Open
woahwhattheheck wants to merge 15 commits into
woahwhattheheck wants to merge 15 commits into
Conversation
* ci: remove invalid top-level retention-days from GitHub Actions workflows * ci: remove invalid retention-days from build.yml * ci: drop invalid top-level retention-days and restore secrets script
woahwhattheheck
force-pushed
the
sol56/payd501-advisory-leader-20261004
branch
from
October 6, 2026 05:44
de38187 to
819b2b1
Compare
Author
|
/claim #501 Original-author GrantFox OSS/FWC26 contribution and conditional compensation claim: I, @woahwhattheheck (GitHub account ID 293286387), submit this original contribution for issue #501 and affirmatively claim contributor credit and consideration for any eligible bounty compensation under the campaign terms. Please confirm eligibility, acceptance criteria, award amount (if applicable), and payment instructions. No award or payment is presumed. |
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.
Fixes #501
Summary
PoolClient, keeping the advisory lock bound to one session for each scheduler passrunInProgressfence so one replica cannot overlap its own scheduled cyclesValidation
Current carrier head:
51b502bdd3db1ca8b5b17552cc648885c5fe115a— 15 commits, 4 issue-scoped files (two services and their focused regression files).The UUID ownership, renewal, and status-fencing regressions were authored but not run. Historical build/test and E2E results predate these source changes and are not evidence for current scheduler/failover behavior.
Exact-head build run
37742203154and secrets run37742202194completed as failure with 0 jobs created. No current-head scheduler execution, production multi-replica soak, or failover benchmark is established.Contribution and payment
The existing /claim #501 and original contributor/payee @woahwhattheheck remain in place. I am claiming this delivered contribution and requesting the applicable GrantFox Third Campaign payment. Please confirm eligibility, assignment, the reward amount, and the payout method and timing. Application, acceptance, award, and settlement are separate decisions.