Open GoogleCodeExporter opened 9 years ago
which fields specifically are 0?
libtorrent provides 3 different sources for these counters.
int list_peers;
int list_seeds;
int num_complete;
int num_incomplete;
int num_seeds;
int num_peers;
If this does not turn out to be a mistake in deluge, using the wrong field or
having misunderstood what they mean, it would be great if you could provide a
response from the tracker (can be captured with wireshark) just to confirm that
the tracker does in fact report counters > 0, and which ones.
Original comment by arvid.no...@gmail.com
on 20 May 2013 at 3:38
Both the number of seeders and peers report 0 even when a peer is connected and
downloading. That peer then completes and becomes another seeder but the number
of seeders stays at 0.
I think this is an issue with some private trackers only. Check the screenshot
attached. The top 2 seeding items for mame sets are on the pleasuredome private
tracker which is ok but the bottom ST no-intro set is on Rutracker which is the
problem.
uTorrent under windows reports all stats correctly so maybe they work out the
stats differently ?
Original comment by david.dm...@gmail.com
on 20 May 2013 at 4:15
Attachments:
This is comment is from a while ago. Someone else having an issue with the same
tracker.
http://forum.deluge-torrent.org/viewtopic.php?f=7&t=31185&start=20
Original comment by david.dm...@gmail.com
on 20 May 2013 at 4:19
Same issue with Ru Tracker so maybe not a bug but reporting method is different
?
http://forum.deluge-torrent.org/viewtopic.php?f=7&t=35975&p=151121&hilit=Rutrack
er#p151121
I am not a dev so no idea how utorrent or other windows clients work the stats
out.
Original comment by david.dm...@gmail.com
on 20 May 2013 at 4:24
That screenshot of deluge is not all that relevant for libtorrent
unfortunately. It's relevant for a bug report against Deluge, not libtorrent.
The output from libtorrent is 6 numbers (the ones I mentioned earlier):
int list_peers;
int list_seeds;
int num_complete;
int num_incomplete;
int num_seeds;
int num_peers;
These are documented here:
http://www.rasterbar.com/products/libtorrent/manual.html#torrent-status
In order to figure out if this is a bug (in libtorrent) or not, it is necessary
to know which ones of those numbers are 0, and why they would be expected to
not be zero. A wireshark dump of one tracker announce would be appropriate for
instance.
I would expect a deluge developer to file this bug and to be able to provide
this information. I would not expect an end-user of deluge to know the internal
of deluge enough to be able to answer this question.
Original comment by arvid.no...@gmail.com
on 23 May 2013 at 3:47
The screenshot shows:
Seeders: num_seeds (num_complete)
Peers: num_peers-num_seeds (num_incomplete)
Original comment by caluml...@gmail.com
on 23 May 2013 at 6:46
Sorry should have added that if num_complete or num_incomplete is -1 then the
value, in braces, is not shown, this means the counters are as follows:
num_complete = -1
num_incomplete = -1
num_peers = 0
num_seeds = 0
Original comment by caluml...@gmail.com
on 23 May 2013 at 8:25
Original issue reported on code.google.com by
david.dm...@gmail.com
on 20 May 2013 at 2:43