Fix qBittorrent 5.x login failure

[GriffTanen]

Description

configure_rpc qbittorrent and any subsequent RPC call fail against qBittorrent 5.x with a confusing message:

ERROR: QBittorrentRPC: Failed to query RPC `http://<host>:8068/api/v2/auth/login`: OK
ERROR: QBittorrentRPC: Failed to login using `http://<host>:8068/api/v2/` RPC: OK
ERROR: Walk failed. Reason: OK

The credentials are correct — the login actually succeeds. qBittorrent 5.x replies to /api/v2/auth/login with HTTP 204 and an empty body, while earlier versions replied 200 with the body Ok.:

HTTP/1.1 204 OK
set-cookie: QBT_SID_8068=...; HttpOnly; path=/

Two checks reject that valid response:

1. query() — if response.status_code != 200: treats 204 as a failure and raises with response.text.strip() or response.reason. The body is empty, so the message becomes the reason phrase OK, which is why the errors above read Reason: OK.
2. login() — if result.text != 'Ok.' requires the exact Ok. body, which 5.x no longer sends.

Changes

• query() accepts any 2xx status instead of exactly 200.
• login() treats an empty body as success alongside Ok., so both qBittorrent 4.x and 5.x work.

Verification

Tested against qBittorrent 5.1.4 (Web API on port 8068), torrt 1.2.0, Python 3.12.

Before the change torrt walk fails at login. After:

INFO: Torrent walk is triggered
INFO: Torrent walk is started
INFO: Getting torrents from `qbittorrent` ...
INFO:   Processing `Lanterns (Season 1) WEB-DL 1080p`...
INFO:     No updates
INFO: Torrent walk is finished

add_torrent also works end to end — the torrent is fetched from the tracker and added to the client:

INFO: Torrent from `https://rutracker.org/forum/viewtopic.php?t=...` is added within `qbittorrent`

Database Migration

NO

[idlesign]

Thank you. I'd like to ask you to add a test for this scenario.

[coveralls]

Coverage Report for CI Build 33210945552

Coverage increased (+0.3%) to 67.972%

Details

• Coverage increased (+0.3%) from the base build.
• Patch coverage: 2 of 2 lines across 1 file are fully covered (100%).
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	1686
Covered Lines:	1146
Line Coverage:	67.97%
Coverage Strength:	3.86 hits per line

---

💛 - Coveralls

[coveralls]

Coverage Report for CI Build 33127488465

Coverage remained the same at 67.675%

Details

• Coverage remained the same as the base build.
• Patch coverage: 2 of 2 lines across 1 file are fully covered (100%).
• 1 coverage regression across 1 file.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

1 previously-covered line in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
src/torrt/rpc/qbittorrent.py	1	87.63%

---

Coverage Stats

Relevant Lines:	1686
Covered Lines:	1141
Line Coverage:	67.67%
Coverage Strength:	3.85 hits per line

---

💛 - Coveralls

[GriffTanen]

Sure — added in d6793cc.

test_login_qbittorrent_5 covers the reported scenario: a login answered with 204 and an empty body, followed by a regular call to confirm the session is usable. It fails on the unpatched code with

Failed to login using `http://localhost:8080/api/v2/` RPC: No Content

and passes with the fix.

test_login_failed keeps the negative path covered, so an unexpected body is still reported as an authentication failure rather than being swallowed by the widened check.

Both use the existing response_mock style of the module. Locally the qBittorrent suite goes 5 → 7 passed; the 4 unrelated failures I see (test_main.py::test_fullcycle and the eniahd/kinozal/nnmclub tracker tests) are present on the branch point too, so they are not caused by this PR.

[idlesign]

Thank you. Merged.