Repository navigation
fix(registry): record tree-truncation verdict to stop hourly refails - #254
Merged
Merged
Conversation
harlan-github-agent
Bot
added
harlan-agent-running
Contributor
Author
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. 84ae6da6-55e0-4f94-a059-7684109b77f0 |
harlan-github-agent
Bot
added
harlan-agent-ready
This was referenced Sep 18, 2026
harlan-github-agent
Bot
removed
the
harlan-agent-ready
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 #252
❓ Type of change
📚 Description
posthog/posthog has failed the hourly sync with
tree_truncatedon every run, 28 failed jobs in the issue's window. The truncated-tree branch in the sync bailed with a failed status but never wrote anything to the repos row, sorepo_meta_synced_atstayed stale and both candidate sweeps re-picked the repo each hour, paying the same five GitHub calls for the same guaranteed failure.The sync now records the outcome on the repos row (
tree_truncated_at, migration 0118) and both sweeps skip rows carrying it. Any later successful repo write clears the verdict, so a repo that becomes fetchable again returns to the normal freshness cycle.Each already-too-large repo will fail once more the first time the sweep picks it after deploy, then goes quiet. posthog/posthog is not picked again after that. The asset-backfill path reports "tree truncated" separately and is untouched; it is not driven by the hourly sweep.