A download whose response declares a Content-Length re-arms its attempt
timeout on every chunk, so a server that trickles just above the throughput
floor was never cut off by time. Parallel downloads also had no shared limit
on the disk they could fill.
- Each download attempt now has a deadline that incoming data never moves:
30 minutes by default, HYPERFRAMES_MAX_DOWNLOAD_MS to change it. Passing it
fails the download without a local retry.
- The default per-file cap drops from 20 GiB to 8 GiB
(HYPERFRAMES_MAX_DOWNLOAD_BYTES still overrides it).
- Downloads keep 512 MiB free on their volume
(HYPERFRAMES_DOWNLOAD_MIN_FREE_BYTES, 0 turns it off). A declared size is
claimed before the body is read and counted against every parallel
download on the same device, and free space is measured again every 4 MiB
as bytes arrive. Free space that cannot be measured does not block.
- docs/packages/engine.mdx lists the download limits and their variables.
downloadToTemp now refuses any Content-Encoding other than identity, caps each
download at 20 GiB (HYPERFRAMES_MAX_DOWNLOAD_BYTES) on the declared Content-Length
and while streaming, and aborts a transfer whose bytes over the last 60 s average
below 32 KiB/s (HYPERFRAMES_MIN_DOWNLOAD_BYTES_PER_SEC, 0 disables).
Compressed and over-limit responses are not retried. A throughput abort is a
retryable timeout like the stall timer, which is unchanged. A sized body that
trickles one chunk every 100 s is now cut by the floor instead of finishing.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(engine): ffmpeg steps and downloads stop on no progress, not while still advancing
* test(cli): an ffmpeg step that stops advancing reports inactivity, not a deadline