min interval is innacurate about libtorrent HOT 5 CLOSED

Here is an example, first announce response is correct (tracker interval is 30 minutes), and all other are errors

announce timestamps:
1345798762 | this is first announce, event = started
1345798795 |
1345798800 |
1345798810 |
1345798830 |
...

this is single tracker torrent btw and I'm using latest git code. Why is this happening ?

Thanks !

from libtorrent.

When requesting more peers, if denied it goes into failure mode rather than waitiing until min request timer finishes.

I'll look into a fix.

from libtorrent.

The min_interval issue has been fixed.

from libtorrent.

--- src/torrent/tracker.h,orig  2012-09-25 21:56:47.607686352 +0200
+++ src/torrent/tracker.h   2012-09-25 22:01:13.731684611 +0200
@@ -150,4 +150,4 @@

-  void                set_normal_interval(int v)            { if (v >= 600 && v <= 3600) m_normal_interval = v; }
-  void                set_min_interval(int v)               { if (v >= 300 && v <= 1800) m_min_interval = v; }
+  void                set_normal_interval(int v)            { m_normal_interval = std::min(std::max(600, v), 3600); }
+  void                set_min_interval(int v)               { m_min_interval = std::min(std::max(300, v), 1800); }

This also contributes to the problem (and this diff fixes it), since current code ignores values that are considered out of range, instead of normalizing them into the range,

from libtorrent.

Fixed.

from libtorrent.