flood
flood copied to clipboard
Start command for Transmission client executes "Start Now" command, skipping download queue
Your Environment
- Version used: latest docker release as of posting
- Environment name and version: Firefox latest
- Operating system and version: Windows 10
- Torrent client and version: Transmission: 3.00 (0), RPC: 16
Summary
Pressing start on a paused (stopped) torrent starts the torrent immediately, bypassing the download queue. The queue should be respected unless the user executes a force command.
Expected Behavior
Start should execute "start", and allow Transmission to queue or start the torrent as appropriate.
Current Behavior
See summary.
Possible Solution
The start context menu item should execute the correct "start" command, and an additional "start now" context menu item should exist that executes the present "force start" or "start now" function in Transmission.
Steps to Reproduce
- Set transmission download queue to enabled and with a value greater than the downloading torrent count, eg. 1:
Transmission settings.json
"download-queue-enabled": true, "download-queue-size": 1,
- Start >queue size torrents.
- Restart transmission, extra torrents should be paused/queued (status seems to be differentiable)
- Start a new torrent through Flood
- Observe that it is started rather than queued