Custom Query (2449 matches)
Results (253 - 255 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2953 | Fixed | code typo (ex -> e) in move_storage() preventing 'move storage' error from being proper logged | ||
| Description |
Nothing happens when attempting to move storage under certain conditions. The error from deluged.log is below. I believe it is a simple typo - the last argument to log_error should be e (the error reported), not ex (which doesn't exist). The code snippet from torrent.py is also below. The deluged.log generates this error: Code highlighting: [ERROR ] 10:50:08 rpcserver:304 Exception calling RPC request: global name 'ex' is not defined
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/deluge/core/rpcserver.py", line 299, in dispatch
ret = self.factory.methods[method](*args, **kwargs)
File "/usr/lib/python2.7/site-packages/deluge/core/core.py", line 411, in move_storage
if not self.torrentmanager[torrent_id].move_storage(dest):
File "/usr/lib/python2.7/site-packages/deluge/core/torrent.py", line 913, in move_storage
self.torrent_id, dest, ex)
NameError: global name 'ex' is not defined
Lines 906 - 914 in deluge/core/torrent.py, the 'ex' in the line next to last should be 'e': Code highlighting: if not os.path.exists(dest): try: # Try to make the destination path if it doesn't exist os.makedirs(dest) except OSError, e: log.error("Could not move storage for torrent %s since %s does " "not exist and could not create the directory: %s", self.torrent_id, dest, ex) return False |
|||
| #2952 | Fixed | appdata.xml file for Linux software gallery integration | ||
| Description |
AppData is an open standard for displaying end user meta data in centralized software stores. |
|||
| #2951 | Fixed | Merge fix for #1908 into 1.3 | ||
| Description |
The patch for #1908 allows the WebUI to bind to a particular IP address. This feature is conspicuously missing from the WebUI considering the daemon has supported it for quite some time. The patch (49d4bb49697289ffd9052a3a43d2a74a452a18f6) has sat in the develop branch for nearly three years. Please consider merging this into the next 1.3 release. This is a small feature that is independent from the rest of Deluge (no backwards incompatibility issues), but affords us the control to completely lockdown remote access to Deluge (binding to localhost, accessing with a proxy). Or, on servers with multiple IPs, one can now open the WebUI port selectively, not on every IP. |
|||
