fddd462ff36fd25015474d9d8f1bb81df302ba0c
let a torrent start re-downloading Batch-relinking 9 torrents, one setLocation call silently failed (status ignored) while the script declared success and moved on. Its recheck then ran against the original (now-empty) path, found 0% match, and qBittorrent started re-downloading the whole torrent from scratch into its incomplete-files staging area. No lasting harm (separate path from the real hardlinked copy, cleaned up), but caught only by watching qBittorrent directly, not by anything the script reported. Fixes: every mutating call now goes through an api_call() helper that checks the HTTP status and aborts on failure; the torrent is stopped before any location/rename calls (qBittorrent 5.x renamed pause/resume to stop/start) and left stopped after recheck rather than auto-resuming, so a bad relink can never turn into an active download. setLocation's effect is also verified via a follow-up GET before proceeding to renameFile. Claude-Session: https://claude.ai/code/session_01HZQK6jHmdTpFjFZM8FUnqA
docker-infrastructure
Languages
Shell
58.2%
Python
28%
JavaScript
10.5%
HTML
2.3%
DIGITAL Command Language
0.6%
Other
0.4%