Repository navigation
Preserve UI history after Sonarr and Radarr cleanup - #30
Merged
Merged
Conversation
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.
Sonarr and Radarr cleanup currently removes completed and failed jobs from magnetowid’s UI history. Archive those records in the existing database so they remain visible for 90 days from completion and survive restarts.
Archived records stay out of the SABnzbd API history. The UI retains their original result, marks them Archived, and only offers record removal. Removing an archive cannot delete files, including when a newer download has reused the old folder. Existing records already deleted are not restored.
Validation:
make test: formatting, vet, and race tests passed, including persistence, retention, API filtering, and file safety.make integration: Sonarr and Radarr passed import, cleanup, and archive persistence checks across restarts. The synthetic-media fixtures skip free-space checks because their advertised sizes exceed the tiny files they download.