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
sentry-checkin: Nitro's built-in route cache (defineCachedEventHandler) forwards its already-caught best-effort KV write failures to Sentry as unhandled errors (SKILLD-17, KV PUT failed: 429), while project policy in shared/server/cache.ts records the same #117
Nitro's built-in route cache (defineCachedEventHandler) forwards its already-caught best-effort KV write failures to Sentry as unhandled errors (SKILLD-17, KV PUT failed: 429), while project policy in shared/server/cache.ts records the same failure class as a wide event, so the server Sentry config needs a beforeSend filter for this exact signature with the wide event kept as the visibility path.
The sentry-checkin routine opened this issue automatically on its 2026-09-01T20:20: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 end to end in installed deps: nitropack 2.13.4 runtime/internal/cache.mjs catches its route-cache KV setItem failure and calls useNitroApp().captureError(error, { event, tags: ['cache'] }); @sentry/nuxt 10.73.0 sentryCloudflareNitr
Next action: Implement isBestEffortCacheWriteError in shared/sentry.ts matching the exact best-effort cache-write signature, wire it as a beforeSend filter on the sentryCloudflareNitroPlugin options in server/plugins/sentry.ts, and add test/unit/sentry-
Activity
harlan-github-agent commentedon Sep 1, 2026
🤖 ISSUE TRIAGE
fix: resolve issue #117 (#153)
harlan-zw commentedon Sep 7, 2026
Fixed by #153 (merged 2026-09-07): nitro route-cache KV write failures are dropped in beforeSend.