mirror of
https://github.com/Lidarr/Lidarr.git
synced 2026-03-03 00:26:58 -05:00
Lidarr removes files after importing already existing content #1342
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
Area: Update API
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Don't Merge
Status: Help Wanted
Status: In Progress
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
conflict
no-conflict
not-pulled
radarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Lidarr-Lidarr#1342
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @suikerchiller on GitHub (Dec 24, 2020).
Describe the bug
Bumping into unexpected behavior with manual imports. When an album incl its content already exist in Lidarr and I try to import the same identical content via "Wanted / Manual Import", the original file gets removed to make place for the upgrade. But when I check back, the upgraded file isn't there either. Both files are removed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
You would expect the find the same content in the library, while the export directory is empty. The reason why I apply this flow is because I'm doing a bulk import moving most of my library into Lidarr. Doing it this way allows me to make sure that I don't forget to import anything and know everything has been imported into my library when the export directory is empty.
Platform Information (please complete the following information):
AB#3361
@bakerboy448 commented on GitHub (Jul 13, 2022):
still occurring in v1?
trace logs that bug reports require?