lukaszraczylo c811de3dfb test(yaegi-check): probe the mid-body-stall half of the watchdog too ...

exerciseRequestTimeout only drove a provider that never sends headers,
so it exercised Transport.ResponseHeaderTimeout alone.
watchdogBody.fire — the interpreted method value handed to
time.AfterFunc, plus context.CancelFunc and sync/atomic's function API
— never ran under that probe, since the request never got far enough
to construct a watchdogBody at all (finding F7, coordinator
adversarial review, 2026-08-23).

Adds hungbody, a provider whose upstream sends headers immediately and
then stalls, and exerciseRequestTimeoutMidBodyStall to drive it.

Verified the two probes exercise different code paths: removing
watchdogBody's construction from upstreamBytes left the existing
header-timeout probe passing unchanged, while the new probe failed
with status 200 instead of 502. Reverted before this commit.

2026-08-23 02:53:53 +01:00

..

pricing-sync

fix(pricing): content-digest snapshot instead of a wall-clock date

2026-08-22 02:12:29 +01:00

yaegi-check

test(yaegi-check): probe the mid-body-stall half of the watchdog too

2026-08-23 02:53:53 +01:00