Custom Query (2449 matches)
Results (628 - 630 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2123 | WontFix | Custom destination path should add without "move on complete" | ||
| Description |
When a torrent is manually added, and the user types in a custom destination path, it makes no sense to tick the "Options - Move Completed" box in the torrent's options. Example: Preferences - Default download path: ~/Downloads/incoming/, Move completed downloads to: ~/Downloads/complete/ Now the user adds a torrent, and the target path field of course defaults to ~/Downloads/incoming/, but the user instead types /storage/ and adds it like that. The user has made the choice of where they want the file. Therefore, the "Options - Move Completed" box for that torrent should not be ticked, since the user obviously knows where they want the file to be placed. |
|||
| #2127 | WontFix | select() reactor has problems with >1024 File Descriptors | ||
| Description |
The select reactor has issues with more than 1024 file descriptors, which leads to errors like this when having a large number of connections. I'm not sure what the best path to take in this situation is. Either we could integrate with twistd, which does it's own intelligent reactor selection, or write logic to determine whether we're on Linux, and if so, opt for the poll() or epoll() reactor, and select() otherwise. Traceback (most recent call last):
--- <exception caught here> ---
exceptions.ValueError: filedescriptor out of range in select() Unhandled error in Deferred: Traceback (most recent call last):
--- <exception caught here> ---
exceptions.KeyError: <type 'instance'> |
|||
| #2153 | WontFix | Improper Torrent Loading (Duplication of Files) | ||
| Description |
As of 1.3.5 deluge makes a copy of every torrent in the state folder under AppData when it is loaded. I don't believe this is efficient when the option to store torrents in a separate directory is turned on. Another issue I have noticed is that if you are loading a torrent from the same directory as the directory set to copy your .torrent files to it will replace the existing file instead of realizing that the file is already in the right place. Running deluge version 1.3.5 with libtorrent 0.16.1 on win32 |
|||
