Opened 6 years ago

#6159 new Bug

delay in RPC of torrent status when starting/stopping

Reported by: meowmix Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.92
Severity: Normal Keywords:


When toggling a torrent through the RPC with torrent-{start,stop}, it looks like there is a delay after already getting back success from the rpc before the value of status actually changes after stopping the torrent. This can be seen by toggling with transmission-remote and immediately asking for info:

$ transmission-remote -t 11 -S && transmission-remote -t 11 -i $ transmission-remote -t 11 -s && transmission-remote -t 11 -i

the status from both lines will read "Idle" or whatever, but never "Stopped". I don't know if this is just a problem with status and/or the torrent-start/stop methods.

What I would expect is that a torrent-get request after receiving success from a torrent-{start,stop} request return that the status of the torrent is {started,stopped} respectively; unless an error has occurred.

Change History (0)

Note: See TracTickets for help on using tickets.