mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Allow image cleanup #7095
Reference in New Issue
Block a user
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 @enter-a-random-username on GitHub (Jun 13, 2025).
Description of the bug
Some person/people are without an image. (It seems anidb wants an image, but it can't be loaded). If I click the trash bin I get an exception. Only way to fix it so far, is to overwrite it with another metadata provider → No other image is no possible fix without altering the DB.
Trying uploading a new image
Deleting the image (rest f the log in in the log section)
Reproduction steps
What is the current bug behavior?
What is the expected correct behavior?
if file exsits is false -> skip the deleteJellyfin Server version
Master
Specify commit id
23c2528Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.11.0
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@Shadowghost commented on GitHub (Jun 13, 2025):
Just to make sure I understand it correctly: Somehow the provider creates an Image entry in the DB but no actual file on the drive, so now it fails to delete the bad entry if you do it manually?
@enter-a-random-username commented on GitHub (Jun 13, 2025):
I think it was/is a bug in anidb or API change or so. Metadata works and I have no 0 byte XML in cache.
Selection
URL
Writer has an image on anidb. In general, it seems the mapping to person has some issues at the moment. I don't see any links to anidb. Can't remember
@sjorge commented on GitHub (Jun 14, 2025):
0 byte XML is probably because it tried to download one when the client was ratelimited. I think a while ago there was an attempt to fix this, but I think there are still edge cases where you can end up with a invalid XML in the cache.
Edit, hmm just a match on the banned XML payload I think, not when you keep going and it just refuses to reply.
7a29589b59is already 3 years old.Wouldn't surprise me some bogus/bad date got send to jellyfin and somepoint that now shows it's ugly head after the conversion to EFCore.
@enter-a-random-username commented on GitHub (Jun 14, 2025):
What? I wrote NO 0 byte, so that is not the issue.
That is not the issue with missing images, everything else loads. Even images for show, only person fails.
I didn't report anything because that repo is not very active and complicated with UDP API and XML HTTP limited. I clean up the 0 byte files and restart the process 12 h later or so. It works. Unrelated to this.
@sjorge commented on GitHub (Jun 14, 2025):
Sorry, my brain skipped over the NO.