mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Run external program parameter is incorrect when "keep incomplete torrents in" is used. #2885
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#2885
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 @AlexHimself on GitHub (Aug 3, 2015).
All of these settings are located under
Tools>Options, Downloadsand I'm using v3.2.3Setup
I am using the Run external program feature with a bug.
I have "Keep incomplete torrents in" turned on with the directory:
The "Save files to location is"
Issue
If I download a folder
FOO, upon download completion, the external program will produceBut the expected output and actual file location would be:
Test/Repro batch file
Here is a batch file I used to test this:
And the external command to run under the the options is:
@sledgehammer999 commented on GitHub (Aug 4, 2015):
This is fixed by #3457 and #3497 for v3.3.0 (currently unreleased). However, it will not be backported in the v3.2.x series. The codebases of the 2 series are quite different.
@AlexHimself commented on GitHub (Aug 4, 2015):
Great to hear, any guess on the release of v3.3.0? :)
@sledgehammer999 commented on GitHub (Aug 4, 2015):
No. But if you aren't using trackers that ban alpha/beta versions you can go to the forum and download the latest beta.