media: bypass qbit_manage's qBittorrent version ceiling #383

Merged
mysticalsoap merged 1 commit from fix/qbit-manage-version-check into trunk 2026-10-07 18:18:20 -04:00
Owner

Problem

qbit_manage v4.13.0 only accepts qBittorrent up to 5.2.3 (a version compare against its bundled qbittorrent-api). qBittorrent moved to 5.2.4 on 2026-10-01, and every scheduled run since 2026-10-02 00:00 exited at that check with CRITICAL before running a single command. No alert fires on that path (webhooks.error is empty by design), so it went unnoticed for six days: 26 torrents added since then had no tracker tags, including every bookshelf-audio torrent, and no share-limit or unregistered cleanup ran.

Fix

skip_qb_version_check: true in media/qbit_manage/config.yml, with a comment on why. Setup page gets the gotcha and the "check the next run reached Executed Commands" step after a qBittorrent bump.

Verification

Live, 2026-10-07, with the edited config bind-mounted: docker exec qbit_manage python3 qbit_manage.py --run logged the [BYPASS] warning and completed. Afterwards every torrent is tagged (661 of 661, previously 643 of 669 with the 26 untagged all added after 2026-10-01); the eleven bookshelf-audio torrents carry MyAnonaMouse or IPTorrents by announce host; nine torrents whose library copy is no longer hardlinked (five movie upgrades, four albums) received noHL and the noHL-iptorrents share limit, and eight torrents were removed by the catch-up cleanup.

🤖 Generated with Claude Code

## Problem qbit_manage v4.13.0 only accepts qBittorrent up to 5.2.3 (a version compare against its bundled `qbittorrent-api`). qBittorrent moved to 5.2.4 on 2026-10-01, and every scheduled run since 2026-10-02 00:00 exited at that check with `CRITICAL` before running a single command. No alert fires on that path (`webhooks.error` is empty by design), so it went unnoticed for six days: 26 torrents added since then had no tracker tags, including every bookshelf-audio torrent, and no share-limit or unregistered cleanup ran. ## Fix `skip_qb_version_check: true` in `media/qbit_manage/config.yml`, with a comment on why. Setup page gets the gotcha and the "check the next run reached `Executed Commands`" step after a qBittorrent bump. ## Verification Live, 2026-10-07, with the edited config bind-mounted: `docker exec qbit_manage python3 qbit_manage.py --run` logged the `[BYPASS]` warning and completed. Afterwards every torrent is tagged (661 of 661, previously 643 of 669 with the 26 untagged all added after 2026-10-01); the eleven bookshelf-audio torrents carry `MyAnonaMouse` or `IPTorrents` by announce host; nine torrents whose library copy is no longer hardlinked (five movie upgrades, four albums) received `noHL` and the `noHL-iptorrents` share limit, and eight torrents were removed by the catch-up cleanup. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
media: bypass qbit_manage's qBittorrent version ceiling
All checks were successful
validate / validate (pull_request) Successful in 24s
a56c77589a
qbit_manage v4.13.0 refuses qBittorrent 5.2.4 at startup (its bundled
qbittorrent-api knows up to 5.2.3) and exits before any command runs, so
every scheduled run since the 5.2.4 merge failed the same way with no
alert. The ceiling is a version string compare; the API did not change.
Skip the check so a routine qBittorrent patch bump cannot silently stop
tagging and cleanup again.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
mysticalsoap deleted branch fix/qbit-manage-version-check 2026-10-07 18:18:21 -04:00
Sign in to join this conversation.
No description provided.