RuntimeError: dictionary changed size during iteration
Issue #73
resolved
Using deluge 2.1.1 with YaRSS2-2.1.5-py3.9 I found this in the log
17:58:39 [WARNING ][yarss2.core :48 ] YaRSS2.rssfeed_scheduler:94: An exception was thrown by the RSS update handler. Please report this bug!
Traceback (most recent call last):
File "/home/eli/.config/deluge/plugins/YaRSS2-2.1.5-py3.9.egg/yarss2/rssfeed_scheduler.py", line 90, in rssfeed_update_handler_safe
return self.rssfeed_update_handler(rssfeed_key=rssfeed_key, subscription_key=subscription_key)
File "/home/eli/.config/deluge/plugins/YaRSS2-2.1.5-py3.9.egg/yarss2/rssfeed_scheduler.py", line 107, in rssfeed_update_handler
fetch_result = self.rssfeedhandler.fetch_feed_torrents(self.yarss_config.get_config(), rssfeed_key,
File "/home/eli/.config/deluge/plugins/YaRSS2-2.1.5-py3.9.egg/yarss2/rssfeed_handling.py", line 373, in fetch_feed_torrents
self.fetch_feed(subscription_data, rssfeed_data, fetch_data)
File "/home/eli/.config/deluge/plugins/YaRSS2-2.1.5-py3.9.egg/yarss2/rssfeed_handling.py", line 442, in fetch_feed
self.log.info("Not adding because of old timestamp: '%s'" % matches[key]["title"])
File "/home/eli/.config/deluge/plugins/YaRSS2-2.1.5-py3.9.egg/yarss2/util/logging.py", line 42, in info
self.handle_gtkui_log(message, gtkui)
File "/home/eli/.config/deluge/plugins/YaRSS2-2.1.5-py3.9.egg/yarss2/util/logging.py", line 34, in handle_gtkui_log
self.gtkui_log_message_event(message)
File "/home/eli/.config/deluge/plugins/YaRSS2-2.1.5-py3.9.egg/yarss2/util/logging.py", line 61, in gtkui_log_message_event
component.get("EventManager").emit(GtkUILogMessageEvent(message))
File "/usr/lib/python3/dist-packages/deluge/core/eventmanager.py", line 28, in emit
component.get('RPCServer').emit_event(event)
File "/usr/lib/python3/dist-packages/deluge/core/rpcserver.py", line 549, in emit_event
for session_id, interest in self.factory.interested_events.items():
RuntimeError: dictionary changed size during iteration
Comments (2)
-
repo owner -
repo owner - changed status to resolved
- Log in to comment
Hi
This has been resolved here: https://dev.deluge-torrent.org/ticket/3351