[libtorrent] trackers in resume data

Discussion:

Michael Mckeown

2016-07-05 22:48:18 UTC

If you add a torrent that has trackers in it that are off line then when
you save the resume data and then restart the torrent from the resume
data then the offline trackers are gone from the list, is there an
option to keep them?

Michael Mckeown

2016-07-08 12:36:05 UTC

Permalink

This might be related as well.

(announce_entry) is_working ( ) returns true no matter what,
torrent_error_alert will show the tracker as 404 but is_working ( )
still remains true, force_reannounce ( ) will trigger the
torrent_error_alert but is_working ( ) still is true.

But also to clarify the first post the saved resume data includes the
torrent file itself so its restarting everything from the resume.

Thanks.

Post by Michael Mckeown
If you add a torrent that has trackers in it that are off line then
when you save the resume data and then restart the torrent from the
resume data then the offline trackers are gone from the list, is there
an option to keep them?

Arvid Norberg

2016-07-24 22:06:12 UTC

Permalink

this is not a case I believe has been thoroughly considered. I believe the
intention of not including trackers that are failing in the resume data is
if they were _manually_ added. Perhaps that fact needs to be captured
somehow, or perhaps this logic should just change.

Is the tracker not included in the resume data despite is_working() returns
true?

do you have any suggestions of how to fix this?

Post by Michael Mckeown
This might be related as well.
(announce_entry) is_working ( ) returns true no matter what,
torrent_error_alert will show the tracker as 404 but is_working ( )
still remains true, force_reannounce ( ) will trigger the
torrent_error_alert but is_working ( ) still is true.
But also to clarify the first post the saved resume data includes the
torrent file itself so its restarting everything from the resume.
Thanks.

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Libtorrent-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss

--
Arvid Norberg

Michael Mckeown

2016-07-27 13:54:45 UTC

Permalink

well is_working() is always true even if the tracker is offline yet
somehow the resume data knows the tracker is offline and does not store it.

Conceptually though, to me, I think the resume should simply store all
trackers even if offline as there is no way to know the tracker wont
come back online again soon. There is the tracker_error_alert message to
delete persistent troublesome trackers if needs be.

I've been looking a bit more into the trackers and with the
create_lt_trackers_plugin you do tend to get quite a few additional
trackers added but the resume does not store these even if they are online.

Post by Arvid Norberg
this is not a case I believe has been thoroughly considered. I believe the
intention of not including trackers that are failing in the resume data is
if they were _manually_ added. Perhaps that fact needs to be captured
somehow, or perhaps this logic should just change.
Is the tracker not included in the resume data despite is_working() returns
true?
do you have any suggestions of how to fix this?