Closed ensisoft closed 6 years ago
I think the issue here is that the command list cancellation is checked on a NNTP command granularity which means that in this case the previous LIST command is still running even though the list Task was deleted.
Added a in-flight check for cmdlist cancellation but only when the command is "slow" command. Currently only the LIST command is expected to run very slow.
This is because there's really no way to properly cancel the command other than close the socket. Normal cancellation happens in-between command executions.
Do a listing update, then do for example a download (single connection).
The task is queued, connection is active and transferring data but nothing happens on the task.