Author	SHA1	Message	Date
Simon Chrzanowski	3bbb5aa7a3	Give the detached fetch test time on slow runners ... TestServerKeepsFetchAfterClientHangsUp gave the upstream fetch 5s to start and the follow-up request 5s to be answered. On a Windows CI runner, where the whole test took 13s, the follow-up timed out awaiting headers with nothing wrong. The test checks the outcome, not the speed, so allow 30s for both. A real hang still fails.	2026-10-14 18:14:06 +02:00
Christian Heim	094a962697	At most 64 fetches keep running after their client hangs up; beyond that a fetch is tied to its client again, so nobody can start an unbounded number of large downloads and leave. A server test now checks that client requests actually get the detach marker.	2026-10-12 00:02:02 +02:00