-
Notifications
You must be signed in to change notification settings - Fork 15
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
Error processing duplicates #14
Comments
The error should show up in the terminal window you're running |
Thanks! The problem is the constant stream of access log data, so it's hard to tell from the terminal window. I ran that command, and the logfile is 400mb, so no email :) This is the last part of the file callback:
It seems like a file is not decodable, but which one? |
I see. Looks like a corrupted image, I should handle that better, thanks for sharing! Two options:
|
I started doing this manually, but there are too many of them. I guess most of the files which are 1.5k in size are likely corrupt. There are many thousand of them and I can't batch delete them all. If I were to-do item 2 of your suggestions, then I would likely run into the same quota issues and end up with many corrupt image files again. I guess we need an error handler to not download files when quota is hit from Google Photos and instead exit so the user can run it again later. Thanks @mtalcott ! |
Got it. I'm not sure what corrupted them, I will play around with responses after quota is hit and see if I can reproduce and handle. |
Actually @jkowall, could you download one of the corrupted files and post here? That will help diagnose. |
Yep here you go. Looks like it's a 403 :)
|
All fixed, thanks @mtalcott ! Worked like a charm, and 430 less duplicates. |
Seemed to be running, but I think I hit some rate limits. The task was moving forward slowly. Finally it got an error in the web UI, but I am not sure which logs to check. Might be good to add to the docs:
The text was updated successfully, but these errors were encountered: