allow bypassing announce queue #8026
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arvidn
reviewed
Sep 7, 2025
Owner
arvidn
left a comment
arvidn
left a comment
There was a problem hiding this comment.
I like this idea. But rather than passing around a bool priorty, I think it would make sense to make this a tracker_request_flag_t and make it part of the tracker_request
Owner
|
it should probably also be incorporated with "connection boost", so newly added torrents take priority over existing ones, for the first announce |
Author
|
I don't think I understand what connection boost is or does tbh |
Owner
|
I made a slightly tweaked version of this idea, here: #8054 |
Author
|
neato! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When adding a torrent to a client with a lot of torrents, its announce (as far as I understand) is pushed to the end of a queue that could take a while to be processed.
As a workaround if I need to leech immediately, I'd just restart my client and the newer torrents would be added at the top of the queue, but it's rather inelegant.
I'd like a flag for force re-announce to bypass that queue for the torrent to start faster. This PR compiles, but I'm not familiar with the codebase whatsoever so this might not be the appropriate approach. For instance, I'm not sure about how this may or may not be related to https://www.libtorrent.org/reference-Torrent_Handle.html#queue_position_top()
This is more of a feature request than a PR