fix(actions): move registry retirement off saturated runner lane - #1684
Merged
seonghobae merged 4 commits intoSep 2, 2026
Conversation
|
Warning Review limit reachedNext included review available in 12 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
seonghobae
added
bug
ChatGPT Codex Connector
seonghobae
deleted the
fix/registry-retirement-runner-capacity-20260902
branch
September 2, 2026 05:54
seonghobae
added a commit
that referenced
this pull request
Sep 2, 2026
) QUEUE_SATURATION_CHICKEN_EGG: exact head 265b5fa is mechanically mergeable, 0 behind current protected main at verification, and changes only the registry-retirement one-shot, its focused regression contract, and doctoring. Protected-main run 33596622523/job 100141255712 proved #1684 escaped the saturated runner lane but failed before mutation because the complete workflow registry returned zero matches for the first deleted legacy path. The repair treats zero legacy matches as terminally absent, exactly one as disable/read-back, duplicates as fail-closed, while replacement and self remain exact-one. Independent execution of the exact shell logic proved absent->success+self-disable, duplicate->fail-before-self-disable, and visible-active->disable+read-back; focused contract/YAML parsing also passed. There are no exact-head submitted reviews, CHANGES_REQUESTED reviews, or inline review comments, and no observed exact-head failing check; required/security workflows are queued in the same central capacity condition this migration must relieve. Active ruleset 17921150 permits OrganizationAdmin bypass. This merge bypasses only queue-bound admission evidence; it does not bypass a failing test, security finding, conflict, or substantive unresolved review objection.
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
ubuntu-24.04toubuntu-slimafter its post-refactor(actions): consolidate 18 hourly review-repair callers into one file #1673 migration job remained queued behind the saturated standard-runner control-plane backlog.actions: write+contents: read, no checkout/provider credentials, replacement-active proof before mutation, exact workflow identity enumeration, read-after-write verification, fail-closed unexpected-state handling, and self-disable last.ubuntu-24.04orubuntu-latest.Live incident evidence
The migration run created by merged PR #1673, run
33589796226/ job100121288663, remained queued onubuntu-24.04while the central Actions backlog was saturated. This one-shot exists specifically to retire 18 obsolete workflow registry identities, so leaving the retirement transaction on that same saturated lane creates an avoidable operability dependency.Test plan
tests/test_hourly_review_repair_registry_retirement.pypins the runner and retains every existing privilege/state-transition invariant.