OpenListTeam / OpenListTeam/OpenList
[BUG] aria2 下载整个文件夹,部分文件大小只有几B
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24.7k
- Forks
- 2.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
Please confirm the following
-
I have read and agree to AGPL-3.0 Section 15 .
The program is provided "as is" without any warranties; you bear all risks of using it. -
I have read and agree to AGPL-3.0 Section 16 .
The copyright holders and distributors are not liable for any damages resulting from the use or inability to use the program. -
I confirm my description is clear, polite, helps developers quickly locate the issue, and complies with community rules.
-
I have read the OpenList documentation.
-
I confirm there are no duplicate issues or discussions.
-
I confirm this is an
OpenListissue, not caused by other reasons (such as network, dependencies, or operation). -
I believe this issue must be handled by
OpenListand not by a third party. -
I confirm this issue is not fixed in the latest version.
OpenList Version (required)
v4
Storage Driver Used (required)
夸克 115
Bug Description (required)
aria2 下载整个文件夹,如果里面文件很多,最终下载后,有些文件会丢失,只有几B大小
这个是什么问题,或者有什么其他解决方案;测试夸克和115都会
Configuration File Content (required)
Logs (optional)
No response
Reproduction Link (optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a full-folder aria2 download on OpenList v4 using the Quark and 115 storage drivers, then compare the missing files and their reported sizes. The issue provides configuration screenshots but no logs or reproduction link, so collect logs and a minimal reproducible case first. Done means the affected files download completely rather than being missing or only a few bytes.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100