starred/Cleanuparr
1
0
Fork 0
mirror of https://github.com/Cleanuparr/Cleanuparr.git synced 2026-06-12 23:29:36 -05:00
Code Issues 38 Packages Projects Releases 10 Wiki Activity

Viewing strikes #154

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

Originally created by @guipace on GitHub.

Is there a way to view the number of strikes a download has received?

I've configured the app, but can't tell if it's actually counting strikes towards removing the downloads. I also don't see any related info in the logs.

Thanks!

Originally created by @guipace on GitHub. Is there a way to view the number of strikes a download has received? I've configured the app, but can't tell if it's actually counting strikes towards removing the downloads. I also don't see any related info in the logs. Thanks!
giteasync commented 2025-10-09 16:59:47 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

No reason in particular. I just thought it would make sense for the number of strikes to be on debug, as they are not as important, and the actual removal and reason to be on info. Everything is up for debate though, so please tell me what you think makes more sense.

@Flaminel commented on GitHub: No reason in particular. I just thought it would make sense for the number of strikes to be on `debug`, as they are not as important, and the actual removal and reason to be on `info`. Everything is up for debate though, so please tell me what you think makes more sense.
giteasync commented 2025-10-09 16:59:47 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

Enabling debug logging should start showing logs about the number of strikes an item has. By default, the logs show only when an item is removed due to receiving the max amount of strikes.

@Flaminel commented on GitHub: Enabling debug logging should start showing logs about the number of strikes an item has. By default, the logs show only when an item is removed due to receiving the max amount of strikes.
giteasync commented 2025-10-09 16:59:47 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

Are there any items in the queue that should receive strikes? Are you using the latest docker image and enabled removing items with a certain number of strikes?

@Flaminel commented on GitHub: Are there any items in the queue that should receive strikes? Are you using the latest docker image and enabled removing items with a certain number of strikes?
giteasync commented 2025-10-09 16:59:48 -05:00
Author
Owner
Copy Link

@oldretepzold commented on GitHub:

image

Obviously not OP but can confirm strikes are logged. However, I am curious why the current strike level is log level debug but everything else is info?

Could see it useful for some sort of CLI tool to get current strike info though.

@oldretepzold commented on GitHub: ![image](https://github.com/user-attachments/assets/a3cb6a67-afcc-4822-b03e-51d2247f926e) Obviously not OP but can confirm strikes are logged. However, I am curious why the current strike level is log level `debug` but everything else is `info`? Could see it useful for some sort of CLI tool to get current strike info though.
giteasync commented 2025-10-09 16:59:48 -05:00
Author
Owner
Copy Link

@guipace commented on GitHub:

Forgot to mention I had already enabled debug logging. No strike info there.

@guipace commented on GitHub: Forgot to mention I had already enabled debug logging. No strike info there.
giteasync commented 2025-10-09 16:59:49 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

I'm glad it works!

@Flaminel commented on GitHub: I'm glad it works!
giteasync commented 2025-10-09 16:59:49 -05:00
Author
Owner
Copy Link

@guipace commented on GitHub:

I can now view strikes. The issue was that I an on unraid and the application template used there was out of date.
Thanks @Flaminel for taking it over and providing a more correct one.

@guipace commented on GitHub: I can now view strikes. The issue was that I an on unraid and the application template used there was out of date. Thanks @Flaminel for taking it over and providing a more correct one.
giteasync commented 2025-10-09 16:59:49 -05:00
Author
Owner
Copy Link

@Flaminel commented on GitHub:

Could see it useful for some sort of CLI tool to get current strike info though.

I did think of the possibility to add an API to cleanuperr, but it's not really a priority, especially if I can't find enough use cases for it. If you've got any more ideas, I'd be happy to receive any feature requests!

@Flaminel commented on GitHub: > Could see it useful for some sort of CLI tool to get current strike info though. I did think of the possibility to add an API to cleanuperr, but it's not really a priority, especially if I can't find enough use cases for it. If you've got any more ideas, I'd be happy to receive any feature requests!
giteasync commented 2025-10-09 16:59:49 -05:00
Author
Owner
Copy Link

@oldretepzold commented on GitHub:

No reason in particular. I just thought it would make sense for the number of strikes to be on debug, as they are not as important, and the actual removal and reason to be on info. Everything is up for debate though, so please tell me what you think makes more sense.

Not a big deal, I would just assume they'd all be under info or all under debug.

@oldretepzold commented on GitHub: > No reason in particular. I just thought it would make sense for the number of strikes to be on `debug`, as they are not as important, and the actual removal and reason to be on `info`. Everything is up for debate though, so please tell me what you think makes more sense. Not a big deal, I would just assume they'd all be under info or all under debug.
giteasync commented 2025-10-09 16:59:49 -05:00
Author
Owner
Copy Link

@oldretepzold commented on GitHub:

Could see it useful for some sort of CLI tool to get current strike info though.

I did think of the possibility to add an API to cleanuperr, but it's not really a priority, especially if I can't find enough use cases for it. If you've got any more ideas, I'd be happy to receive any feature requests!

Yeah not particularly high priority, just could be useful for a quick lookup vs looking through logs.

@oldretepzold commented on GitHub: > > Could see it useful for some sort of CLI tool to get current strike info though. > > I did think of the possibility to add an API to cleanuperr, but it's not really a priority, especially if I can't find enough use cases for it. If you've got any more ideas, I'd be happy to receive any feature requests! Yeah not particularly high priority, just could be useful for a quick lookup vs looking through logs.
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
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#154
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?