Skip to content

v0.21.0

Choose a tag to compare

@jasonodoom jasonodoom released this 09 Nov 02:43
· 11 commits to main since this release
v0.21.0
41ef6da

Large or unreliable-connection uploads no longer have to restart from zero: a NAR of 64 MiB or more now uploads in resumable parts.

Added

  • NARs of 64 MiB or more upload in parts through the control plane's multipart
    routes. Each part is retried on its own under the same inactivity timeout as a
    single PUT, so a stall costs one part. A job re-run after an interrupted
    upload resumes from the parts the control plane has recorded rather than from
    zero, with no state kept on the runner. A session that expires, is aborted or
    is being completed by an overlapping run is waited for or restarted within the
    same run. NARs past R2's 4.995 GiB single-PUT limit can be uploaded, up to the
    control plane's multipart limit. R2 checks each part against its MD5 only; the
    control plane verifies the assembled NAR's SHA-256 before accepting it. A
    control plane without multipart support still receives a single PUT.