starred/Cleanuparr-Cleanuparr
1
0
Fork 0
mirror of https://github.com/Cleanuparr/Cleanuparr.git synced 2026-02-04 21:38:07 -06:00
Code Issues 38 Packages Projects Releases 10 Wiki Activity

[BUG] Changing unlinked downloads category has weird behavior with Transmission #52

New Issue
Closed
opened 2025-10-09 16:57:09 -05:00 by giteasync · 7 comments
giteasync commented 2025-10-09 16:57:09 -05:00
Owner
Copy Link

Originally created by @denysdovhan on GitHub.

Before submitting a bug report, I have:

  • Reviewed the documentation.
  • Ensured I am using ghcr.io/cleanuparr/cleanuparr docker repository.
  • Ensured I am using the latest version.
  • Enabled verbose logging.

What is the behavior?

I am using Transmission, and it seems like Cleanuparr doesn't handle changing the download category well. For example, I have this folder structure:

.
├── data
│   ├── movies
│   └── tv
└── downloads
    ├── movies
    └── tv

As you see tv and movies are categories. I have this configuration in Cleanuparr:

Image

With this configuration I expect unlinked downloads to end up alongside movies and tv, but instead it is placed within these directories as moves/orphaned and tv/orphaned:

.
├── data
│   ├── movies
│   └── tv
└── downloads
    ├── movies
    │   └── orphaned
    └── tv
        └── orphaned

However, this is only part of the issue. At the end of the day, I'd like to have downloads completely removed from download client. Can we have an option to remove downloads, alongside of changing category.

Which operating system do you use?

Linux

What type of deployment do you use?

Docker container

Relevant log output

Anything else?

My compose.yaml

  cleanuparr:
    image: ghcr.io/cleanuparr/cleanuparr:latest
    container_name: cleanuparr
    restart: unless-stopped
    env_file: .env
    volumes:
      - ${DOCKER}/cleanuparr:/config
      - ${MEDIA_VOLUME}/downloads:/downloads # for monitoring orphaned downloads
    ports:
      - 11011:11011
Originally created by @denysdovhan on GitHub. ### Before submitting a bug report, I have: - [x] Reviewed the documentation. - [x] Ensured I am using ghcr.io/cleanuparr/cleanuparr docker repository. - [x] Ensured I am using the latest version. - [x] Enabled verbose logging. ### What is the behavior? I am using Transmission, and it seems like Cleanuparr doesn't handle changing the download category well. For example, I have this folder structure: ``` . ├── data │ ├── movies │ └── tv └── downloads ├── movies └── tv ``` As you see `tv` and `movies` are categories. I have this configuration in Cleanuparr: <img width="923" alt="Image" src="https://github.com/user-attachments/assets/b61d3938-6ec9-49d0-a00e-ed8019d9d8eb" /> With this configuration I expect unlinked downloads to end up alongside `movies` and `tv`, but instead it is placed within these directories as `moves/orphaned` and `tv/orphaned`: ``` . ├── data │ ├── movies │ └── tv └── downloads ├── movies │ └── orphaned └── tv └── orphaned ``` However, this is only part of the issue. At the end of the day, I'd like to have downloads completely removed from download client. Can we have an option to remove downloads, alongside of changing category. ### Which operating system do you use? Linux ### What type of deployment do you use? Docker container ### Relevant log output ```shell ``` ### Anything else? My `compose.yaml` ```yaml cleanuparr: image: ghcr.io/cleanuparr/cleanuparr:latest container_name: cleanuparr restart: unless-stopped env_file: .env volumes: - ${DOCKER}/cleanuparr:/config - ${MEDIA_VOLUME}/downloads:/downloads # for monitoring orphaned downloads ports: - 11011:11011 ```
giteasync added the
bug
 label 2025-10-09 16:57:09 -05:00
giteasync commented 2025-10-09 16:57:12 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

Yes, I meant in Cleanuparr.

@Flaminel commented on GitHub: Yes, I meant in Cleanuparr.
giteasync commented 2025-10-09 16:57:12 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

So, if I understand it correctly:

  1. Unlinked Download Settings should just mark orphaned downloads with a category, let's say orphaned.
  2. Then seeding rule for orphaned should remove downloads from the download client, when applied.

This is correct.

The moving part is totally up to Transmission to do it correctly - Cleanuparr just calls Transmission to handle that, it does not move it by itself. Any idea why there's a problem on your setup? Also, if you remove one of those orphaned downloads, do the files also get permanently deleted? If so, you can probably ignore the "missing" part that Transmission warns about.

@Flaminel commented on GitHub: > So, if I understand it correctly: > > 1. Unlinked Download Settings should just mark orphaned downloads with a category, let's say orphaned. > 2. Then seeding rule for orphaned should remove downloads from the download client, when applied. This is correct. The moving part is totally up to Transmission to do it correctly - Cleanuparr just calls Transmission to handle that, it does not move it by itself. Any idea why there's a problem on your setup? Also, if you remove one of those `orphaned` downloads, do the files also get permanently deleted? If so, you can probably ignore the "missing" part that Transmission warns about.
giteasync commented 2025-10-09 16:57:12 -05:00
Author
Owner
Copy Link

@denysdovhan commented on GitHub:

If you want the download from the orphaned category to be removed, you have to set up a seeding rule for it. Why would this be an issue?

You mean seeding rule in Cleanuparr? AFAIK, transmission doesn't have seeding rules.

@denysdovhan commented on GitHub: > If you want the download from the orphaned category to be removed, you have to set up a seeding rule for it. Why would this be an issue? You mean seeding rule in Cleanuparr? AFAIK, transmission doesn't have seeding rules.
giteasync commented 2025-10-09 16:57:12 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

With this configuration I expect unlinked downloads to end up alongside movies and tv, but instead it is placed within these directories as moves/orphaned and tv/orphaned

This is done to avoid moving files from a filesystem to another, which would take time and resources. Why is your example the better solution?

However, this is only part of the issue. At the end of the day, I'd like to have downloads completely removed from download client. Can we have an option to remove downloads, alongside of changing category.

If you want the download from the orphaned category to be removed, you have to set up a seeding rule for it. Why would this be an issue?

@Flaminel commented on GitHub: > With this configuration I expect unlinked downloads to end up alongside `movies` and `tv`, but instead it is placed within these directories as `moves/orphaned` and `tv/orphaned` This is done to avoid moving files from a filesystem to another, which would take time and resources. Why is your example the better solution? > However, this is only part of the issue. At the end of the day, I'd like to have downloads completely removed from download client. Can we have an option to remove downloads, alongside of changing category. If you want the download from the `orphaned` category to be removed, you have to set up a seeding rule for it. Why would this be an issue?
giteasync commented 2025-10-09 16:57:12 -05:00
Author
Owner
Copy Link

@denysdovhan commented on GitHub:

Oh, it seems like I've got it wrong.

So, if I understand it correctly:

  1. Unlinked Download Settings should just mark orphaned downloads with a category, let's say orphaned.
  2. Then seeding rule for orphaned should remove downloads from the download client, when applied.

The problem for me, Transmission doesn't seem to handle changing categories well. For some reason when download is moved, Transmission UI says it's missing, since the directory was changed.

@denysdovhan commented on GitHub: Oh, it seems like I've got it wrong. So, if I understand it correctly: 1. Unlinked Download Settings should just mark orphaned downloads with a category, let's say `orphaned`. 2. Then seeding rule for `orphaned` should remove downloads from the download client, when applied. The problem for me, Transmission doesn't seem to handle changing categories well. For some reason when download is moved, Transmission UI says it's missing, since the directory was changed.
giteasync commented 2025-10-09 16:57:13 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

No problem!

@Flaminel commented on GitHub: No problem!
giteasync commented 2025-10-09 16:57:13 -05:00
Author
Owner
Copy Link

@denysdovhan commented on GitHub:

Okay, I've played with it a bit, and it seems like it's actually working properly, even though it moves files to orphaned subfolder.

Thanks for clarifying that for me!

@denysdovhan commented on GitHub: Okay, I've played with it a bit, and it seems like it's actually working properly, even though it moves files to `orphaned` subfolder. Thanks for clarifying that for me!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
planned
pull-request
Mirrored from GitHub Pull Request
question
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Cleanuparr-Cleanuparr#52
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?