mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
bug: spamming recursive label copy #2798
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#2798
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 @snoukkis on GitHub (Jul 16, 2015).
I ended up with really many recursive copies of a torrent and others which I relabeled together.
Steps:
Expected result:
Torrent download folder should contain: foldername\foldername...;foldername\otherrelabeledtorrent...;etc.
Actual result:
Torrent download folder contains an endless list of foldername\foldername\foldername\foldername\foldername\foldername\etc. , each containing all the files of each relableled torrent. To be fair the recursion did seem to stop at some point and didn't crash anything either. It did hang for a moment though when I tried to open the location from "Content" panel.
Environment:
@ngosang commented on GitHub (Jul 19, 2015):
I tested v3.3.0 alpha and this problem is fixed. If this problem is annoying you try downloading 3.3.0 https://qbforums.shiki.hu/index.php/topic,3606.0.html
@sledgehammer999 commented on GitHub (Jul 19, 2015):
Yes, try 3.3.0. It haves major changes in handling paths. However those changes cannot be backported to the v3.2.x series.
@snoukkis commented on GitHub (Jul 19, 2015):
Good to hear path handling is improved in future releases. Does that change have an issue?
Offtopic: does the changed path handling fix problems with multiple torrents downloading into same subdirectory/files?
@sledgehammer999 commented on GitHub (Jul 19, 2015):
If you download into the same file it can never be fixed. You should ask libtorrent-rasterbar to handle that issue.
The change doesn't have an issue, they are part of a major code refactoring and shouldn't be backported to the stable branch. (although 3.3.0 is very stable anyways)