fix(transmission): always start added torrents - #206
Merged
Merged
Conversation
The live settings.json had start-added-torrents=false (the image default is true), so a Catch/showRSS magnet added at 01:30 sat Stopped and never fetched its metadata. Nothing in the repo set the value, so a runtime change persisted across restarts. Pin it via env in both podman run blocks so updateSettings.py rewrites it to true on every container start.
This comment has been minimized.
This comment has been minimized.
This file contains hidden or 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
1 participant
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.
When Catch adds a showRSS magnet, Transmission leaves it Stopped, so it never fetches metadata and never downloads. It should start on its own. The S04E10 Strange New Worlds magnet added at 01:30 on 2026-09-24 sat there all night. The live settings.json had start-added-torrents set to false. The haugene image defaults it to true and nothing in this repo sets it, so a runtime change from the web UI or RPC stuck across restarts. I don't know when or how it got flipped.
Pins TRANSMISSION_START_ADDED_TORRENTS=true in both podman run blocks, the initial setup and the supervisor wrapper that recreates the container. updateSettings.py rewrites env-backed keys on every start, so the value can't drift again. It takes effect on the next container recreate, not a restart. The live session was already switched with transmission-remote --no-start-paused, and the torrent is downloading.