Repository navigation
Unpinned skills answer a permanent 503 retry loop on skills-raw #577
Copy link
Copy link
Open
Labels
harlan-agent-wait-to-implementIssue triage found work that should wait before implementation.Issue triage found work that should wait before implementation.routine:daily-checkin
Description
Activity
- addedharlan-agent-runningAn Agent holds a Task on this issue or pull request right now.An Agent holds a Task on this issue or pull request right now.
on Oct 8, 2026 harlan-github-agent commented
on Oct 8, 2026 ContributorAuthorMore actions🤖 ISSUE TRIAGE
Harlan Agent Kit posted this automated triage. It is not Harlan's personal assessment or commitment. AI open source policy.
- Route: Wait to implement
- Difficulty: 1/5
- Impact: 2/5
- Reproduction: Yes
- Codebase review: Not needed
- 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;
- Next action: Close Unpinned skills answer a permanent 503 retry loop on skills-raw #577 as resolved by fix(registry): complete large repository source refresh #575, citing the verification evidence: the trigger URL answers 410 because the source is gone upstream (raw.githubusercontent 404), and production D1 holds zero rows matching the permanent-503 conditions. Do not implement the default_branch fallback; closing also stops the daily-checkin fingerprint from re-offering it.
- 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.
- addedharlan-agent-wait-to-implementIssue triage found work that should wait before implementation.Issue triage found work that should wait before implementation.harlan-agent-runningAn Agent holds a Task on this issue or pull request right now.An Agent holds a Task on this issue or pull request right now.and removedharlan-agent-runningAn Agent holds a Task on this issue or pull request right now.An Agent holds a Task on this issue or pull request right now.
on Oct 8, 2026
Metadata
Metadata
Assignees
Labels
harlan-agent-wait-to-implementIssue triage found work that should wait before implementation.Issue triage found work that should wait before implementation.routine:daily-checkin
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).
Target:
layers/registry/server/api/skills-raw/[...slug].get.tsVerify with:
curl -s -o /dev/null -w '%{http_code}\n' 'https://skilld.dev/api/skills-raw/posthog/posthog/diagnosing-experiment-results/references/qualitative-feedback.md'Estimated to change 3 files.