Opened 9 years ago

Closed 9 years ago

Last modified 6 years ago

#2235 closed bug (Fixed)

gtkui exception after add torrent

Reported by: tyeken8 Owned by:
Priority: major Milestone:
Component: GTK UI Version: 1.3.5
Keywords: Cc:

Description

Sometimes gtkui didn't update after add a torrent, debug said exceptions.KeyError? (on the new torrent), seems the new torrent's info didn't received (sth. wrong in core or lost in the net).

Unhandled error in Deferred:
Traceback (most recent call last):
  File "twisted/internet/tcp.py", line 460, in doRead

  File "deluge\ui\client.py", line 183, in dataReceived

  File "twisted/internet/defer.py", line 280, in callback

  File "twisted/internet/defer.py", line 354, in _startRunCallbacks

--- <exception caught here> ---
  File "twisted/internet/defer.py", line 371, in _runCallbacks

  File "deluge\ui\sessionproxy.py", line 182, in on_status

exceptions.KeyError: 'ac8eed4...'

Change History (4)

comment:1 Changed 9 years ago by Cas

The exception message seems to be missing code details, did you remove them?

comment:2 Changed 9 years ago by tyeken8

  • Summary changed from After add torrent to gtkui exception after add torrent

No, I'm using gtkui on windows.

The sessionproxy code should be

177         # Helper functions and callbacks ---------------------------------------
178         def on_status(result, torrent_ids, keys):
179             # Update the internal torrent status dict with the update values
180             t = time.time()
181             for key, value in result.items():
182                 self.torrents[key][0] = t
183                 self.torrents[key][1].update(value)
184                 for k in value:
185                     self.cache_times[key][k] = t
186
187             # Create the status dict
188             if not torrent_ids:
189                 torrent_ids = result.keys()
190
191             return self.create_status_dict(torrent_ids, keys)

comment:3 Changed 9 years ago by Cas

  • Resolution set to fixed
  • Status changed from new to closed

That particular error has been fixed in 1.3-stable for next release.

comment:4 Changed 6 years ago by Cas

  • Milestone 1.3.x deleted

Milestone deleted

Note: See TracTickets for help on using tickets.