Deluge starts downloading paused torrent on force re-check
Posted: Fri Feb 27, 2015 10:28 pm
Deluge starts downloading paused torrent on force re-check.
Steps:
1) Add a new torrent
a. Do not set the directory or file name of existing files.
b. Check "Add In Paused State".
2) Take note of the status of the torrent, it should be: Paused (0.00%)
3) Do a Force Re-Check on the newly added torrent.
Expected occurence: It should return to it's previous status, Paused (0.00%), after finding no files.
What happens: torrent status go from Paused to Downloading.
4 (optional)) You can try pausing it and force Re-Check again, it will start Downloading again.
It's critical that adding and re-checking works when (re-)adding torrents for existing files, because if the directories don't match the user will be in trouble if Deluge starts re-downloading large amounts of data. Knowing the inherent risk, the user will be cautious and add the torrents in a paused state, but this is currently a trap, because the paused state is overridden if the directory (or file name if single file torrent) doesn't match 100%.
Tested with Deluge 1.3.11 and 1.3.6 on Windows 7 x64, both local drives and on mapped samba shares. The initial report/complaint came to my attention from another user on another forum, I did not discover it myself, but I did test to confirm.
Steps:
1) Add a new torrent
a. Do not set the directory or file name of existing files.
b. Check "Add In Paused State".
2) Take note of the status of the torrent, it should be: Paused (0.00%)
3) Do a Force Re-Check on the newly added torrent.
Expected occurence: It should return to it's previous status, Paused (0.00%), after finding no files.
What happens: torrent status go from Paused to Downloading.
4 (optional)) You can try pausing it and force Re-Check again, it will start Downloading again.
It's critical that adding and re-checking works when (re-)adding torrents for existing files, because if the directories don't match the user will be in trouble if Deluge starts re-downloading large amounts of data. Knowing the inherent risk, the user will be cautious and add the torrents in a paused state, but this is currently a trap, because the paused state is overridden if the directory (or file name if single file torrent) doesn't match 100%.
Tested with Deluge 1.3.11 and 1.3.6 on Windows 7 x64, both local drives and on mapped samba shares. The initial report/complaint came to my attention from another user on another forum, I did not discover it myself, but I did test to confirm.