You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unpinned skills answer a permanent 503 retry loop on skills-raw #577
Since #573, skills-raw and skill-asset answer 503 with retry-after: 30 whenever rendered_commit_sha is NULL, and repos whose sync can never complete (posthog's permanently truncated tree) stay NULL forever, so every referenced-file request retried (Sentry SKILLD-3W, 1,969 events from 10:27Z).
The daily-checkin routine opened this issue automatically on its 2026-10-08T08:23:00.000Z run. It is not Harlan's own report. Close it to reject the proposal, and the reason you give stops it being offered again.
Summary: Verified against production on 2026-10-11: the defect no longer reproduces. The issue's curl now answers 410, not 503, because the post-fix(registry): complete large repository source refresh #575 sync completed posthog/posthog and recorded source_resolved=0 (PostHog deleted the skill upstream;
Related pull requests:fix(registry): complete large repository source refresh #575: Merged root-cause fix: bounded subtree reads complete truncated trees like posthog/posthog and the prioritized sync pool drains unpinned reference-carrying skills; production D1 now shows zero rows in the 503 class, resolving this issue's scenario.; fix(registry): preserve root Skill snapshots #573: Merged change that introduced the reported behavior: 503 with retry-after 30 whenever rendered_commit_sha is NULL in skills-raw and skill-asset, by design transient until the sync pins each repo.
Activity
harlan-github-agent commentedon Oct 8, 2026
🤖 ISSUE TRIAGE