No timeout on fetch/DB/HTTP
Part of the Error handling & resilience check · fix arrives as a guide
What it is
An outbound HTTP request, database query, or socket operation is issued with no timeout configured, relying on the runtime default — which is frequently no timeout at all.
Why it matters
A hung call does not fail, it waits. It holds its worker, its connection, and its memory until something else gives out, which is how a slow third party becomes your outage while their status page stays green.
How to fix it
Set an explicit timeout on every outbound call — an AbortSignal.timeout() on fetch, a statement timeout on queries, a connect and read timeout on clients. Choose a value from the caller's tolerance, not the dependency's p99.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.