Is there already an issue for this request?
Platform
Windows
Describe the enhancement you'd like
Pretty frequently, I get failures that look like this:
warning Fri Nov 29 2024 19:37:38 Skipping unpack for <file> due to par-failure
info Fri Nov 29 2024 19:37:37 No renamed archive files found for <file>
info Fri Nov 29 2024 19:37:37 Checking renamed archive files for <file>
error Fri Nov 29 2024 19:37:37 Repair failed for <file>\1293293ea40f3ad9a141c5c3e9a4bde6868cc780: not enough par-blocks, 178 block(s) needed, but 143 block(s) available. Recovery files created by: ParPar v0.3.2 [https://animetosho.org/app/parpar]
info Fri Nov 29 2024 19:37:37 Need more 178 par-block(s) for <file>\1293293ea40f3ad9a141c5c3e9a4bde6868cc780
These get stuck in my history as failed downloads. But 90% of the time, they download and finish successfully if I use Actions > Retry Failed Articles.
Is there any particular reason no retry gets triggered?
Extra information
No response
Is there already an issue for this request?
Platform
Windows
Describe the enhancement you'd like
Pretty frequently, I get failures that look like this:
These get stuck in my history as failed downloads. But 90% of the time, they download and finish successfully if I use Actions > Retry Failed Articles.
Is there any particular reason no retry gets triggered?
Extra information
No response