-
-
Notifications
You must be signed in to change notification settings - Fork 840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug Report] Generate covers when blob is missing does not work #3657
Comments
I don't use docker, but have you mapped your blobs directory to a persistent location (#3613)? |
@DingDongSoLong4 Yes, I have done that part correctly (now) - thank you :) |
I am not sure ii it will help, but Can you run a clean in dry run and see if it shows the blobs in the logs? |
@MrX292 Good suggestion. It unfortunately shows nothing:
|
I assume the reason why enabling overwrite doesn't actually overwrite existing covers is because you could have manually added them so it wouldn't be overwriting 'existing generated files' as they're then not generated. That does cause the issue you describe where if the cover blob file is deleted then you can't regenerate it. Stash can't really check if each blob exists on every scan, that will likely slow it down considerably with many blobs (or at least I would assume so, would need to test to be sure) so the most obvious fix would be to just make overwrite actually overwrite everything. Now that the Clean task has come up, adding a Clean-like task to remove both invalid blob info from the database and stale blobs from the file system as in #3601 would also solve the issue, and would be a good addition whether or not the overwrite option is changed. |
I can't test it at the moment, but my first guess is that |
@DingDongSoLong4 Absolutely. Running checks everytime it handles a scene would slow things down. But, like you describe, a Clean-like task to go through and verify all cover_blobs would be great - then there is a way to fix this situation, for when it happens. Btw, just as a curiosity, here is the logging (DEBUG level) for running Generate with overwrite on a "broken" scene:
So it says it will generate 1 cover, but it never does. |
Describe the bug
After upgrading to 0.20.2 and deciding to move where my library is located in the filesystem, I have ended up in a situation where a bunch of scenes do not have a cover image showing.
I thought I could just run the generate function and have it create new screenshots for covers, however this does not work.
After digging a bit into it, this is my analysis:
scenes.cover_blob
field, but the corresponding blob file is missing from the blobs directory.To Reproduce
Steps to reproduce the behavior:
Stash Version: (from Settings -> About): v0.20.2 (docker)
The text was updated successfully, but these errors were encountered: