#2925: Wrong peer_id after upgrade
-----------------------+------------------------------------
Reporter: lsorense | Owner:
Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: other (please specify)
Resolution: | Keywords:
-----------------------+------------------------------------
Comment (by lsorense):
So the problem simply is that the peer_id is generated before the
session.state is loaded, which then replaces the peer_id with the old one
from the saved session.state, which in my case was from 1.3.12, and then
continued to set the user agent to 1.3.13, which then causes some picky
trackers to point out that the peer_id and user agent are not in
agreement.
Moving the session.state loading just before the peer_id is created solves
the problem. Not sure why it is ever saved in the session.state in the
first place, unless it is to allow a client to adapt an older saved
session on load if going to a new format in a new client version.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/2925#comment:1>
Deluge <http://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to deluge-dev+unsubscr...@googlegroups.com.
To post to this group, send email to deluge-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
