Skip to content

D1 overload 500s recur after the replayable-read retry fix #192

Closed

Description

@harlan-github-agent

Cold-key crawler sweeps still turn D1 overload into 500s after the #158 retry and #168 stale-serve fixes deployed.

Target: server/utils/db.ts

Verify with: pnpm test:run test/unit/platform-d1.test.ts

Estimated to change 1 file.

The daily-checkin routine opened this issue automatically on its 2026-09-08T21:40: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.

Activity

  1. harlan-github-agent commented on Sep 8, 2026

    @harlan-github-agent
    ContributorAuthor

    🤖 ISSUE TRIAGE

    Harlan Agent Kit posted this automated triage. It is not Harlan's personal assessment or commitment. AI open source policy.

    • Route: Ready to spec
    • Difficulty: 2/5
    • Impact: 4/5
    • Reproduction: Yes
    • Codebase review: Not needed
    • Summary: Real recurrence with production evidence: Sentry SKILLD-1F (295 events, culprit GET /api/skill-related/...) throws bursts after the 2026-09-08 deploy carrying fix(d1): retry replayable reads on D1 overload #158 and fix(cache): serve stale cached responses when a recompute fails #168. Code-level attribution: on a cold cache key, readThroughCache (sha
    • Next action: Write a short spec: confirm from SKILLD-1F event payloads whether the fix(d1): retry replayable reads on D1 overload #158 retries fire and exhaust on the cold-key path, then choose one mitigation (raise retry budget in server/utils/db.ts, per-key single-flight plus cold-key fallback in shared/server/cache.ts, or extend the in-flight SWR work from issues 182-191) and coordinate so it does not duplicate those PRs.
  2. added
    harlan-agent-ready-to-specIssue triage found work that needs a specification before implementation.
    and removed
    harlan-agent-runningAn Agent holds a Task on this issue or pull request right now.
    on Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions