-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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] Backup stuck after 8 elements #106
Comments
Is this photo or video something you can share? Or can you get me the file information from the phone? |
But how do I know which asset it's trying to upload? I have more than 200 items, I don't know which one it's stuck on... |
The assets are uploaded based on chronological order, newest to oldest, you can take a look at all the assets that have been backup and see which one it is trying to upload and track them down from your gallery. |
I've traced it back to a random meme picture in webp format (ZBsUr45_d.webp). Do you need it? |
Ah! |
Oh okay, that makes sense. Thanks c: (Edit: I confirm deleting it fixed the upload queue) |
I'm actually having the same issue with another picture, but it's a This one was taken by my phone (it's a photo of my cat). |
This issue is fixed in #108. I will push out an updated version of the app in the next few days :) Sorry for the inconvenience |
I have a total of 218 assets I want to backup but after uploading 8 of them, the app is stuck at 100% on asset 210.
I cannot see anything in the logs: none of the docker containers shows anything during the upload attempt period (except for redis which says it successfully saved the changes).
I let the app run for over 30min to see if it was just a very slow/long upload, but the problem is still there.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All uploads should succeed.
Screenshots
Server (please complete the following information):
Smartphone (please complete the following information):
Additional context
I also tried without TensorFlow (removed the immich_microservices) but it also fails at the exact same asset.
The text was updated successfully, but these errors were encountered: