Skip to content

fix: skip the README request when the asset has no README.md - #9

Merged
JasonPaff merged 1 commit into
mainfrom
fix/skip-missing-readme-fetch
Sep 28, 2026
Merged

JasonPaff merged 1 commit into
mainfrom
fix/skip-missing-readme-fetch

Conversation

@JasonPaff

Copy link
Copy Markdown
Collaborator

Why

On 2026-09-28 the prod alert alert-atk-prod-failed-requests fired with no server errors. The cause was six GET /assets/skill/*/readme 404s from one session browsing assets that have no README.md. The API is fine; the Functions host counts 4xx as failed requests. (The alert itself is being moved to 5xx only in ADO PR 1577.)

Change

  • useAssetReadme(ref, { enabled }): new optional enabled flag (defaults to true).
  • AssetDetail: the page already loads /files, so it requests /readme only when README.md is listed. It waits for the listing, still asks if the listing fails, and shows the README skeleton while the listing loads.
  • Tests: four route cases (listed / not listed / loading / listing failed) and two hook cases.

Not covered: the bundle page (useBundleReadme) and CLI atk info still get a 404 when there's no README. Bundles have no file listing to check first.

typecheck, lint and vitest run (349 tests) pass.

🤖 Generated with Claude Code

The asset detail page asked GET .../readme for every asset and treated
the 404 as "no README". The Functions host records those 404s as failed
requests, and six of them tripped the prod failed-requests alert on
2026-09-28. The page already loads the file listing, so request the
README only when README.md is listed, and fall back to asking if the
listing fails.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@JasonPaff
JasonPaff merged commit d5f8bb6 into main Sep 28, 2026
1 check passed
@JasonPaff
JasonPaff deleted the fix/skip-missing-readme-fetch branch September 28, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant