[dependabot]

Updated Downloader from 5.9.8 to 5.10.1.

Release notes

Sourced from Downloader's releases.

5.10.1

A small fix on top of 5.10.0 for downloads that use more than one url.

🐛 Fixes

• Each chunk uses its own url again. In 5.10.0 a parallel worker picked one url and used it for every chunk it downloaded, so the url that served a chunk depended on which worker took it. Now chunk i always uses url i % count, the same as before 5.10.0, so the load is spread over your mirrors in a stable way.

5.10.0

Safer live settings, correct file size after a server error, and smarter splitting of the last chunks.

✨ New

• Idle connections can help finish the download. When MinimumChunkSize is set (greater than 0), a parallel worker that has finished its own chunk can split the largest unfinished chunk and download its second half, as long as both halves stay at least MinimumChunkSize. With the default 0 nothing changes. (#​245, thanks @​crazysmile-PhD)

🐛 Fixes

• A server error on the first probe could give a wrong, tiny file reported as complete (#​248). The headers of an error response (for example a 500 with a 41-byte XML body) were read as the file's headers, so the error body's length became the file size. Now only a success or a redirect fills the response headers, so the download really asks again and fails if it never reaches the file.
• Range support is kept after a passing server error. A 500 on the first Range: 0-0 probe no longer switches the download to one connection; the Range probe is asked again. A transient status on the probe (503, 429, 504, 408) is retried up to 3 times instead of failing the download.
• Settings you change during a download are thread-safe (#​247). MaximumBytesPerSecond, ActiveChunks, BufferBlockSize and EnableLiveStreaming use atomic reads and writes, so a change from another thread (like a UI speed limit) is seen by the download threads at once, and PropertyChanged fires once per real change.

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)