Add timeouts to outbound fetches (OIDC discovery/token/JWKS, geocoding) #31

New issue

Open

opened 2026-07-17 03:07:33 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-17 03:07:33 +00:00

Contributor

None of the backend's outbound calls set a timeout: geocode.js:27 (Nominatim), auth.js:158 (OIDC discovery), auth.js:175 (token exchange), auth.js:162 (remote JWKS). A hung upstream stalls the request indefinitely — for the auth routes, that is the login path.

Fix: pass signal: AbortSignal.timeout(8000) (tune per call) to each fetch; createRemoteJWKSet accepts a timeoutDuration option. Return a clear 502/504 with the upstream named. Optionally one retry with backoff for the idempotent discovery/JWKS GETs.

Acceptance criteria

All four call sites time-bounded
Timeout surfaces as an actionable error, not a hang
Geocode failure message names Nominatim

(Audit finding F-10, 2026-07-16 — Severity: Medium, Confidence: High)

None of the backend's outbound calls set a timeout: `geocode.js:27` (Nominatim), `auth.js:158` (OIDC discovery), `auth.js:175` (token exchange), `auth.js:162` (remote JWKS). A hung upstream stalls the request indefinitely — for the auth routes, that is the login path. Fix: pass `signal: AbortSignal.timeout(8000)` (tune per call) to each fetch; `createRemoteJWKSet` accepts a `timeoutDuration` option. Return a clear 502/504 with the upstream named. Optionally one retry with backoff for the idempotent discovery/JWKS GETs. **Acceptance criteria** - [ ] All four call sites time-bounded - [ ] Timeout surfaces as an actionable error, not a hang - [ ] Geocode failure message names Nominatim *(Audit finding F-10, 2026-07-16 — Severity: Medium, Confidence: High)*

claude-bot referenced this issue

2026-07-17 03:09:33 +00:00

Push notifications for stale data and failing jobs (ntfy/webhook) #49

claude-bot added this to the v1.1.0 - Test & Ops Hardening milestone

2026-07-17 03:10:47 +00:00

claude-bot added the

ops

label

2026-07-17 03:11:46 +00:00