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

Avoid redundant requests of announce entries from libtorrent #21949

Merged
merged 1 commit into from
Dec 6, 2024

Conversation

glassez
Copy link
Member

@glassez glassez commented Dec 3, 2024

Schedule request of announce entries of torrent and skip subsequent requests until existing one is done. Otherwise, they can flock in the queue until libtorrent is free to execute them, which leads to multiple overwriting of tracker entry statuses with identical (or even obsolete) data.

@glassez glassez requested a review from a team December 3, 2024 16:01
@glassez glassez added this to the 5.0.3 milestone Dec 3, 2024
@glassez glassez merged commit a180162 into qbittorrent:master Dec 6, 2024
14 checks passed
@glassez glassez deleted the update-tracker-entries branch December 6, 2024 16:59
glassez added a commit to glassez/qBittorrent that referenced this pull request Dec 6, 2024
@HanabishiRecca
Copy link
Contributor

Seems like this change has a serious negative side effect.

Steps to reproduce:

  1. Get a running torrent with Working tracker.
  2. Stop the torrent.
  3. Start the torrent again.

The tracker remains in Not contacted yet state forever. Forcing reannounce does not help.

@HanabishiRecca
Copy link
Contributor

Although, the client does send a network request. But the status remains Not contacted yet and shows N/A in peers.
So there is some internal discrepancy happening.

Reverting this commit fixes the issue.

@glassez
Copy link
Member Author

glassez commented Dec 14, 2024

@HanabishiRecca
Could you test #21995?

@HanabishiRecca
Copy link
Contributor

Seems to be working now.

@xavier2k6
Copy link
Member

@HanabishiRecca good catch!

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

Successfully merging this pull request may close these issues.

4 participants