mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Collation of matches of the same torrent when searching #14561
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#14561
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @asdkant on GitHub (May 1, 2023).
Suggestion
If often happens, especially when using multiple search plugins at the same time, that I get two or more results for the same torrent. It would be nice to get those multiple results collated in a single item, so that when I download that item it merges all the results (same as if I downloaded one, and then tried to download the others merging the tracker information).
If fetching the hash for each result takes more requests than how search works right now, it may be a good idea to keep this feature optional and off by default. Some other criteria like name and download size could be used to filter out matches before checking the hash, since that information is already being fetched by the regular search.
Use case
No response
Extra info/examples/attachments
No response
@thalieht commented on GitHub (May 1, 2023):
Related #2511
@asdkant commented on GitHub (May 3, 2023):
That one seems to be asking the same as me, I'll close this one as duplicate of #2511