Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Negative amount of leechers #65

Closed
stylesuxx opened this issue Mar 15, 2015 · 3 comments
Closed

Negative amount of leechers #65

stylesuxx opened this issue Mar 15, 2015 · 3 comments

Comments

@stylesuxx
Copy link

Hey guys,
On some of the torrents on my tracker I see a negative amount of leechers. This seems to happen on torrents where one or more clients already have the files when adding a torrent, means:

(amount of seeders) = (amount of leechers) * -1 

As soon as a new leecher joins the pool, the amount of leechers goes up, but is still not correct then (at least on those torrents with negative leecher count).

My torrent object looks like so in the moment:

'55600bbcb00fd923dee589655f74900f5abxxxx': { peers: [Object], complete: 2, incomplete: -2 },
 fe0a979f104964e69e8bbc8bcff5bde120d2xxxx: { peers: [Object], complete: 2, incomplete: -1 },
 d3939d09f0a259c5be1cd31cd06499901ca2xxxx: { peers: [Object], complete: 1, incomplete: 0 },

The first torrent has two seeders and no leecher in reality. The Second torrent has two seeders and one leecher. The third torrent seems to be all right, one seeder, no negative leecher and no leecher at all.

Any ideas on this?

@feross
Copy link
Member

feross commented Mar 20, 2015

It would help if you restarted the tracker from scratch, but this time run it with the environment variable DEBUG=bittorrent-tracker Example: DEBUG=bittorrent-tracker node my-tracker.js

Then do the same sequence of new seeders/leechers that you did before and share the tracker output. Thanks!

@feross feross closed this as completed in f1cc540 Apr 21, 2015
@feross
Copy link
Member

feross commented Apr 21, 2015

I believe I've fixed this issue in v3.4.4. If you still encounter negative leechers, please leave a comment or open a new issue.

feross added a commit that referenced this issue May 3, 2015
@feross
Copy link
Member

feross commented May 3, 2015

Attempted a different fix for "Error: value is out of bounds" that should be a more permanent fix. Let me know if you see that error again.

Released as 3.6.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants