AnInsomniacy/aria2-next v3.0.7

v3.0.7 - Intact Files, UTF-8 Torrent Names and Clear Drive Errors

on GitHub

Summary

Aria2 Next 3.0.7 keeps an existing file intact when a server ignores range requests, writes BitTorrent file names correctly under any Linux locale, keeps the Docker image's state directory writable under a custom PUID, and names a missing Windows drive or network share instead of reporting an invalid argument. Release assets cover the same seven platforms.

Fixed

• Continuing a download no longer writes over a file of the same name when the server never offers ranges. The server answers in full, and the body used to be written from byte zero across that file, which could belong to another download; the task now fails with CannotResume and leaves the file as it was, as wget does (rayburst#595).
• BitTorrent file names on Linux are written as UTF-8 whatever the process locale. Under the C locale of a container or service, characters it could not encode became ., so a torrent with Chinese names turned into a hidden folder of dots. The container image also sets LANG=C.UTF-8 for the tools run inside it (#72).
• The Docker image keeps its state directory writable when started with a numeric PUID. HOME used to fall back to /, and adding a torrent failed with "Cannot store torrent data"; the entrypoint now sets HOME=/var/lib/aria2-next after switching user.
• On Windows, a download directory on a drive or network share the engine cannot see now says that the drive or share is not available and suggests its network path, instead of "Invalid argument" or an empty path for media downloads. The usual cause is a drive mapped in another logon session, such as one mapped without administrator rights while the engine runs with them. Downloads to network shares work over UNC paths and mapped drives alike (#74).

Downloads