Fix error added by qbittorrent 5.0 pymedusa/Medusa#11844 #11857
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed fixes for error(s) from #11844 caused by qbittorrent 5.0 api changes, which for reasons unknown to mortal man is that they changed "pause/paused" to "stop/stopped", and "resume/resumed" to "start".
Things addressed/fixed:
Download handler is unable to process completed & "stopped" torrents (completed & uploading/seeding worked fine), which affects people who don't seed or if the download handlers schedule is slower than seeding goal is hit.
Log-level error spawned from not being able to parse this new unknown "stopped" state.
Also tested:
qQbittorrent v4.6.7, to ensure new changes to accommodate qQbittorrent v5.0+ does not negatively affect previous version(s)