Repository navigation
Add jobs/dispatch endpoint and GitHub queued-jobs scanning - #10
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.
What changed
POST /api/v1/jobs/dispatchto the router and executor, which queues and places a job the router never received (or lost) exactly like a webhook-delivered job — by executor priority, honouring capacity and CPU/memory limits — and reports when no executor could take it.GET /api/v1/github/queued-jobson the executor, which scans the installation's repositories for GitHub Actions jobs sitting inqueuedwith no runner, annotated with whether this executor's labels/image accept them.GitHubActionsScanner(cache, repo cap, concurrency limit, timeout, rate-limit floor) plusGitHubScanConfigurationand theGitHubQueuedJobsProvidingprotocol.RouterPendingJobgainspinnedHostnameso dispatch can target one executor through the existinghostCanRunplacement loop.0.25.0; documents the new endpoints and the requiredActions: readinstallation permission in the README.Why
A GitHub Actions job can be reported
queuedwith no VM ever starting for it — a webhook delivery was missed, or an executor lost the job. There was no way to find these or recover them without GitHub credentials of your own. The dispatch endpoint re-places a lost job through the normal placement path, and the queue scan surfaces what GitHub is still waiting on (annotated with which executor can run it).