Deployed 012bf45 with MkDocs version: 1.6.1

This commit is contained in:
2026-10-21 02:09:43 +00:00
parent 0086e55429
commit e4914487fc
4 changed files with 11 additions and 4 deletions
@@ -2464,6 +2464,10 @@ config keys it does not know there, <code>speed_limit</code> for example. <code>
</ul>
<p>Keep a failed download's completed segment files so the next download resumes from where it
stopped instead of restarting from byte zero.</p>
<p>unshackle keeps the segments of a failed track in a <code>resume</code> directory inside the temp
directory, and the next download of the same track takes them back from there. It removes a
kept entry after 7 days, and <code>unshackle env clear temp</code> removes them all. A process that is
killed, or a job cancelled over the REST API, keeps nothing.</p>
<p>unshackle reuses only whole, fully downloaded segments. It always discards partially written
segments, and no partial-byte (<code>Range</code>) resume across runs takes place. Reuse is possible only
with proof that the segmentation did not change. The manifest URL, segment count, and byte