Repository navigation
v0.18.0
A stalled NAR upload no longer consumes the whole job before a retry can run.
Fixed
- The per-attempt upload deadline was a wall-clock allowance scaled to the payload, so a 5 GB NAR was given roughly 85 minutes and a wedged connection sat there for most of it: two multi-GB uploads went 50 and 88 minutes without moving a byte and the 90 minute step cap killed the job before any retry. Uploads are now bounded by INACTIVITY. The clock restarts on every chunk that leaves the process and once more when the body ends, so a silent upload fails in five minutes and retries, while a slow but progressing one runs as long as it needs. A fixed cap cannot make that distinction, and shortening the old allowance would abort large uploads that are working, since a presigned PUT is not resumable and every retry restarts from zero.
Added
- Stall warnings report bytes transferred and the current rate per path (
upload /nix/store/... (5293s in stage, 350 MiB/5.0 GiB, 0 B/s)), so a wedged upload and a slow one are distinguishable from the job log alone.
Changed
VEGA_UPLOAD_STALL_SECONDS(default 300) sets how long an upload may move no bytes before it is aborted and retried.VEGA_UPLOAD_TIMEOUT_SECONDSno longer has any effect; an absolute per-attempt cap isVEGA_UPLOAD_CAP_SECONDS, defaulting to off. The rename is deliberate: reusing the old name would have turned an existing1800into a hard 30 minute kill no multi-GB upload could survive.