Repository navigation
fix(registry): skip tree-truncated repos in render repair sweep - #282
Merged
Merged
Conversation
harlan-github-agent
Bot
added
harlan-agent-running
Contributor
Author
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. 9e2ddd72-ae0d-4ac5-93bf-27488459da74 |
harlan-github-agent
Bot
added
harlan-agent-blocked
harlan-github-agent
Bot
added
harlan-agent-running
harlan-github-agent
Bot
removed
the
harlan-agent-ready
This was referenced Oct 5, 2026
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.
🔗 Linked issue
Closes #280
❓ Type of change
📚 Description
The render-repair sweep kept re-picking posthog/posthog every six hours even though that repo's tree truncates on every GitHub attempt, so each fire queued a render job that could only fail. The daily-checkin issue reports four guaranteed failed jobs on 2026-09-22 (00:25Z, 06:30Z, 12:25Z, 18:25Z) plus a 38-attempt stale-reservation retry loop, all from that one repo.
Both sync sweeps already exclude repos carrying a too-large tree verdict; the repair sweep was missing that guard and now carries it too. While adding it I moved the query next to the other candidate SQL so the three sweeps sit in one file and cannot drift apart silently again. A successful repo write clears the verdict, so an affected skill re-enters the sweep once its repo becomes fetchable.
Follow-up that stays open: the issue's 24-hour post-deploy check,
failed_jobswithexception = 'tree_truncated'returning 0 across four 6-hour fires.