-
Notifications
You must be signed in to change notification settings - Fork 5
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
Deleting non existant images from Trash fails. #25
Comments
Have you tried |
BTW, if you can find a way to reproduce this problem, please let me know. |
I looked at the What you can do to manually fix the problem is:
Let me know if that solves your problem, or if you need more help. |
Repeated calls do not change the output. (only the ordering of the Missing files |
I'll update |
Let `inspect orphans` report and delete (when --delete is set) broken file references in filesets as reported in #25. This exact cause of the broken references is unknown, although it probably happens when files are deleted.
I commited a change to the Before you do anything, I suggest making sure you have a current backup of your data. That's always a good idea. Now, when you run |
Hi, sry, I already did the manual cleanup using Just to be sure, I updated the docker image and run |
OK. If you have that problem again, running |
ok, thank you. |
I have some images in Trash (for quite a long time) that seem to be non existant anymore or in some dubious state, however I can neither delete them directly nor by "clearing" the trash bin.
The frontend is then either stuck (app) or shows a proxy 502 in the webapp (probably exception on the server end).
The text was updated successfully, but these errors were encountered: