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

Incorrect download data sent to private trackers #8383

Closed
MateEke opened this Issue Feb 9, 2018 · 6 comments

Comments

Projects
None yet
6 participants
@MateEke

MateEke commented Feb 9, 2018

qBittorrent version and Operating System

qbittorrent-nox/artful,now 4.0.3.99201801111638-6260-239d14fubuntu17.10.1 amd64

If on linux, libtorrent and Qt version

libtorrent-rasterbar9/artful,now 1.1.6+git20180101.b45acf28a5+patched-configure-1ppa1~artful1 amd64

What is the problem

According to torrent site's staff qBittorrent 4.0.3 reports incorrect download data to tracker. I have reported a problem to them with my ratio and I got this answer:

I recommend u to change ur torrent client immediately. Checking ur stats them are all wrong since u switched to qbitorrent 4.0.3. It is known, reported on github, issuewith this release. Yr client sends incorrect data to tracker.U can downgrade to version 4.0.2. That works fine so far.

I couldn't find a related issue, so I'm reporting.

What is the expected behavior

Send correct data to tracker.

Steps to reproduce

  • Install qBittorrent 4.0.3
  • download something from private tracker with ratio rules
  • check your ratio and realize that it's getting worse and worse
  • cry
@greenbench

This comment has been minimized.

Show comment
Hide comment
@greenbench

greenbench commented Feb 9, 2018

Related issues #8108 and arvidn/libtorrent#2724

@arvidn

This comment has been minimized.

Show comment
Hide comment
@arvidn

arvidn Feb 18, 2018

nobody has so far been able to provide any data to support that incorrect stats are reported. It's essentially impossible to fix any issue unless such evidence can be provided. Anyone experiencing this issue, please provide a log of the tracker announces.

arvidn commented Feb 18, 2018

nobody has so far been able to provide any data to support that incorrect stats are reported. It's essentially impossible to fix any issue unless such evidence can be provided. Anyone experiencing this issue, please provide a log of the tracker announces.

@greenbench

This comment has been minimized.

Show comment
Hide comment
@greenbench

greenbench Feb 18, 2018

Hope it's the right place to ask. Is this app #8108 (comment) launching in "portable mod"? I mean, my qBittorrent.ini and qBittorrent-data.ini in AppData\Roaming will not be overwritten?

greenbench commented Feb 18, 2018

Hope it's the right place to ask. Is this app #8108 (comment) launching in "portable mod"? I mean, my qBittorrent.ini and qBittorrent-data.ini in AppData\Roaming will not be overwritten?

@scrdk

This comment has been minimized.

Show comment
Hide comment
@scrdk

scrdk Mar 20, 2018

@arvidn what happens is this:

On the announce after the event=complete announce, downloaded is incorrectly a few bytes less than the totally downloaded.
E.g. in the attached screenshot, the "green" one is announced incorrectly at the third announce, with less bytes than what was announced at the event=completed, whilst the "blue" one is announced correctly.
I have emailed you the full announces URIs from the attached wireshark capture.

wireshark qb 2

scrdk commented Mar 20, 2018

@arvidn what happens is this:

On the announce after the event=complete announce, downloaded is incorrectly a few bytes less than the totally downloaded.
E.g. in the attached screenshot, the "green" one is announced incorrectly at the third announce, with less bytes than what was announced at the event=completed, whilst the "blue" one is announced correctly.
I have emailed you the full announces URIs from the attached wireshark capture.

wireshark qb 2

@noeltorious

This comment has been minimized.

Show comment
Hide comment
@noeltorious

noeltorious Jun 1, 2018

Am I understanding correctly that this was fixed via arvidn/libtorrent#3025 ?

noeltorious commented Jun 1, 2018

Am I understanding correctly that this was fixed via arvidn/libtorrent#3025 ?

@thalieht

This comment has been minimized.

Show comment
Hide comment
@thalieht

thalieht Jul 28, 2018

Contributor

Am I understanding correctly that this was fixed via arvidn/libtorrent#3025 ?

Yep, closing.

Contributor

thalieht commented Jul 28, 2018

Am I understanding correctly that this was fixed via arvidn/libtorrent#3025 ?

Yep, closing.

@thalieht thalieht closed this Jul 28, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment