Serialize score.yml runs to prevent concurrent DB overload#216
Merged
Conversation
added 4 commits
June 3, 2026 13:14
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
1 participant
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.
Summary
At 100+ miners, multiple agents can merge to main in quick succession, triggering simultaneous score.yml runs. Each run makes dozens of POST /submit calls; concurrent runs risk overwhelming the forge-api SQLite backend.
Changes
concurrency: group: score-main, cancel-in-progress: falseto score.yml — serializes full-score jobs. Pending runs queue (not cancelled), so every merged agent is still scored, just sequentially.