#1
|
|||
|
|||
Downloads stopped one file too early
When I choose "Stop after this download" from the context menu of a file, that file itself isn't downloaded, only the one before it, although it should be downloaded and then JD should stop.
If it helps, I'm currently downloading with Rapidgator and I believe a reconnect is necessary after each file. Last edited by armin.beispiel; 04.07.2022 at 03:03. |
#2
|
||||
|
||||
@armin.beispiel: did you set *stop after this download* on the file that requested the reconnect?
File A, File B(Stopmark) File A -> Reconnect File A finished -> File B -> Reconnect- >Stop? I'm asking because the *Stop after this download* does not mean *stop when this file is downloaded* but *stop when you tried at least once to download the file*, else a broken file (eg waiting, and waiting and waiting) would just make your JDownloader continue to download despite the stopmark being reached.
__________________
JD-Dev & Server-Admin |
#3
|
||||
|
||||
__________________
JD-Dev & Server-Admin |
#4
|
|||
|
|||
Quote:
But it seems you found something to improve that'll likely be the cause. |
#5
|
||||
|
||||
At least for the *reconnect scenario*, yes, that I can improve, maybe that will solve your problem
__________________
JD-Dev & Server-Admin |
#6
|
||||
|
||||
A fix for this scenario is more complex than I though. A download that requires reconnect currently counts as *at least tried once* and thus stop mark is reached. When I change this logic, then a single download waiting for reconnect will cause other links to be started. imagine not having setup a working reconnect, then JDownloader would just continue downloading all the rest.
I've tried a simple solution where JDownloader does allow 1 mins for reconnect to happen and continue. Please check again with next core update. Within that time window new/next downloads may get startet
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 05.07.2022 at 12:47. |
#7
|
|||
|
|||
Couldn't the logic be changed to always handle the stopmark on the next file. So, it is checked as soon as a file starts "Is file after file with stopmark?" If yes, don't continue with the file.
If actions like deactivating files are performed, the internal file-after-stopmark mark would need to be re-evaluated. Maybe your new timeout code (a bit longer?) could function as a fallback, in case of a bug where JD wouldn't stop. |
#8
|
||||
|
||||
@armin.beispiel: changing the behavior is never a good idea please wait for next core update and see if it helps in your situation
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|