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

Alternates between Choke/Unchoke #7695

Open
jech opened this Issue Nov 11, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@jech

jech commented Nov 11, 2017

qBittorrent version and Operating System:

1022 2017/11/11 19:09:40 <- Extended0 qBittorrent/3.3.16

What is the problem:

qBittorrent appears to send a sequence of Choke/Unchoke messages:

1022 2017/11/11 19:12:52 <- Unchoke
1022 2017/11/11 19:12:52 <- Choke
1022 2017/11/11 19:12:52 <- Unchoke
1022 2017/11/11 19:12:52 <- Choke
1022 2017/11/11 19:12:52 <- Unchoke
1022 2017/11/11 19:12:52 <- Choke
1022 2017/11/11 19:12:53 <- Unchoke

What is the expected behavior:

Some hysteresis is applied, so that after a peer has been unchoked, it doesn't get choked straight away.

Steps to reproduce:

This is from a rather large log, so it's not clear how to reproduce.

@Chocobo1

This comment has been minimized.

Show comment
Hide comment
@Chocobo1

Chocobo1 Nov 11, 2017

Member

Is this issue specific to qbittorrent? what about deluge or libtorrent-rasterbar?
And what is your libtorrent-rasterbar version?

Member

Chocobo1 commented Nov 11, 2017

Is this issue specific to qbittorrent? what about deluge or libtorrent-rasterbar?
And what is your libtorrent-rasterbar version?

@jech

This comment has been minimized.

Show comment
Hide comment
@jech

jech Nov 12, 2017

jech commented Nov 12, 2017

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