Drop expected upstream-unavailable 503s from Sentry capture

The skill-files, skill-asset and skills-raw handlers throw their intended upstream-outage 503 as an unhandled error, so Sentry records SKILLD-11 and SKILLD-1E although fetchUpstreamTree already reports the outage as an operational wide event.

Target: shared/sentry.ts

Verify with: pnpm vitest run test/unit/sentry-cache-write-filter.test.ts

Estimated to change 3 files.

The sentry-checkin routine opened this issue automatically on its 2026-09-07T20: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.

🤖 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 implement
Difficulty: 2/5
Impact: 3/5
Reproduction: Yes
Codebase review: Not needed
Summary: skill-files, skill-asset and skills-raw throw createError 503s with three exact messages ('Skill source is unavailable upstream', 'SKILL.md source is unavailable upstream', 'Asset source is unavailable upstream') only after fetchUpstreamTre
Next action: Implementing agent adds an isExpectedUpstreamOutageError predicate to shared/sentry.ts matching the three 'unavailable upstream' 503 signatures (handling Error.message and the Sentry-serialized value, mirroring isBestEffortCacheWriteError),

Navigation Menu

Repository navigation

Drop expected upstream-unavailable 503s from Sentry capture #175

🤖 ISSUE TRIAGE

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Drop expected upstream-unavailable 503s from Sentry capture #175

Description

Activity

harlan-github-agent commented on Sep 7, 2026

🤖 ISSUE TRIAGE

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions