Custom Query (2447 matches)

While running deluge, the following error fills up syslog, emitting a few times a second:

Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]: 09:03:37 [CRITICAL][twisted                       :154 ] Unhandled Error
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]: Traceback (most recent call last):
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:   File "/usr/lib/python3/dist-packages/deluge/core/daemon_entry.py", line 122, in run_daemon
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:     daemon.start()
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:   File "/usr/lib/python3/dist-packages/deluge/core/daemon.py", line 164, in start
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:     reactor.run()
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:   File "/usr/lib/python3/dist-packages/twisted/internet/base.py", line 1283, in run
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:     self.mainLoop()
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:   File "/usr/lib/python3/dist-packages/twisted/internet/base.py", line 1292, in mainLoop
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:     self.runUntilCurrent()
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]: --- <exception caught here> ---
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:   File "/usr/lib/python3/dist-packages/twisted/internet/base.py", line 913, in runUntilCurrent
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:     call.func(*call.args, **call.kw)
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:   File "/usr/lib/python3/dist-packages/deluge/core/core.py", line 345, in _on_alert_session_stats
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:     self._update_session_cache_hit_ratio()
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:   File "/usr/lib/python3/dist-packages/deluge/core/core.py", line 361, in _update_session_cache_hit_ratio
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]:     self.session_status['disk.num_blocks_cache_hits'] / blocks_read
Mar 17 09:03:37 growly /usr/libexec/gdm-x-session[5026]: builtins.KeyError: 'disk.num_blocks_cache_hits'

It occurs immediately after startup and doesn't stop, or rather I can't tell what event it starts on. deluge seems to be working and the errors persist even after the gui is closed. The log spam only stops when I kill deluged.

$ deluge --version
deluge 2.0.3
libtorrent: 2.0.5.0
Python: 3.9.2
OS: Linux Debian GNU/Linux unstable sid

I installed the debian package, which is version "2.0.3-3.1".

Apologies if this is a dupe, I tried to find any similar issues but couldn't.

Traceback (most recent call last):
  File "deluge-debug-script.py", line 33, in <module>
  File "deluge\ui\ui_entry.py", line 62, in start_ui
    options = parser.parse_known_ui_args(sys.argv, withhold=AMBIGUOUS_CMD_ARGS)
  File "deluge\argparserbase.py", line 265, in parse_known_ui_args
  File "deluge\argparserbase.py", line 293, in _handle_ui_options
  File "deluge\log.py", line 158, in setup_logger
  File "logging\__init__.py", line 1146, in __init__
  File "logging\__init__.py", line 1175, in _open
FileNotFoundError: [Errno 2] No such file or directory: 'E:\\Documents\\deluge.log'
[26784] Failed to execute script 'deluge-debug-script' due to unhandled exception!

i have a torrent, which i set "stop seed at ratio" to 2.

what i expected to happen: as soon as the torrent exceeds the ratio of 2, it's automatically stopped regardless of whether or not I'm currently logged into the Web UI

what happened: i log into the Web UI just to see the torrent exceed the upload ratio by multiple amounts of the value I set - the torrent was still active, and it paused after about a second or two after I logged into the Web UI

i think priority of this bug would be "major" at least, as the failure of that feature may potentially result in exceeding upload quotas