Rotorsoft / act-root / 36907262934

100%

push

github

fix(act-http): keep the webhook timeout armed through the response body read (#1712)

fetch resolves on response headers, and clearTimeout sat in the finally
attached to the fetch alone — so the error-path body read ran with no timer
and no signal. A receiver that answered with headers and then never ended
the body hung the reaction handler forever.

A hang is worse than a throw here. The handler never returns and never
raises, so it overruns its lease, the next holder re-claims the stream, and
the attempt never spends its retry budget loudly — the stream never reaches
its blockOnError verdict and never appears in blocked_streams(). That is the
handler.

Hoist the clearTimeout into an outer finally that also wraps the classify
and body read. An abort during the read now reports the timeout rather than
a response that was never finished; a read that fails for its own reasons
stays best-effort and the status verdict still stands.

Closes #1701

Co-authored-by: rotorsoft <rotorsoft@outlook.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

4384 of 4384 branches covered (100.0%)

Branch coverage included in aggregate %.

12 of 12 new or added lines in 1 file covered. (100.0%)

9495 of 9495 relevant lines covered (100.0%)

1231.46 hits per line