Priority Slider & Sequential Check Button are Not Working

[WoAnerges]

Type: Bug Report

• [x] Try to follow the update procedure described in the README and try again before opening this issue.

Your Environment

• Version used:
  • Version (stable release) Yes, 4.8.2
  • Commit ID (development release) N\A
• Environment name and version:
  • Node.js version N\A
  • npm version N\A
  • Web browser latest clean install of Chrome
• Torrent client and version: Transmission 3.00

Summary

Priority Slider & Sequential Check Button are Not Working

Expected Behavior

Expect it to work

Current Behavior

It's not working. Clicking the sequential button doesn't turn it on, and moving the priority slider doesn't change anything.

Possible Solution

Make it work.

Steps to Reproduce

1. run the 4.8.2 deb build
2. have Chome Browser
3. have transmission 3.00
4. try changing the slider and clicking on the sequential check button

Context

Trying to change the download priority and enable the sequential download.

[WoAnerges]

when I press the mentioned buttons I see that cli prints "500" result in red color without any additional info. When I press anything else, green 200 is printed, it's only when I try the sequential button, and the priority slider I see the red 500. I wish it would print more details, so that I could share the output. Otherwise, there's nothing to share from the cli except that.

[trim21]

I don't think transmission 3.00 support such feature, maybe we should hide them in UI when it's a low version of transmission or provide more useful help message

[justinnamilee]

Well, I am on transmission 3.00 and it does seem to offer priority (at least for bandwidth, which is my concern), RPC docs seem to indicate it as well...

justin@kaname:~$ transmission-daemon --version
transmission-daemon 3.00 (bb6b5a062e)

---

justin@kaname:~$ transmission-remote 'http://10.6.6.7:9091/transmission' --torrent 165 --bandwidth-low
10.6.6.7:9091/transmission/rpc/ responded: "success"

justin@kaname:~$ transmission-remote 'http://10.6.6.7:9091/transmission' --torrent 165 -i | grep -i prio
  Bandwidth Priority: Low

justin@kaname:~$ transmission-remote 'http://10.6.6.7:9091/transmission' --torrent 165 --bandwidth-high
10.6.6.7:9091/transmission/rpc/ responded: "success"

justin@kaname:~$ transmission-remote 'http://10.6.6.7:9091/transmission' --torrent 165 -i | grep -i prio
  Bandwidth Priority: High

Now perhaps this isn't what's being used for the priorities in Flood? I don't often need it, but the one time I tried (today) I noticed it didn't seem to be wired up, heh.

Anyway, if it could be hooked up, that'd be cool... but if not 🤷 it isn't the end of the world.