S41: recover stale runner job claims#306
Merged
Merged
Conversation
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.
Summary
Production finding
On 2026-05-17, production had one stale running job assigned to shithub-runner-shared-linux-1 while the runner was heartbeating idle. That consumed the runner's only capacity slot, backed up queued jobs, and eventually suppressed fresh repo-tree status dots when repo queued-run caps were reached. I manually cancelled run/job 67, verified the queue drained, and confirmed production is now idle with zero running workflow jobs.
Deploy note
Deploy web first because the heartbeat decoder rejects unknown JSON fields. Then redeploy shithubd-runner from the same trunk build so it starts sending active_job_ids.
Tests