Closed qrkourier closed 2 years ago
@qrkourier thanks this is very helpful.
I have been unable to test the backoff code in any meaningful way with my connection speed.
when I got throttled on my big account, I let it sit idle for a full day then started back up with a max threads of 5. Delete your bad ids file and try again in a day or two with lower thread settings. worked for me.
@synman @qrkourier UPDATE: I'm now using github actions for CI and it runs multiple targets simultaneously. This is causing me to see HTTP 429.
So I now have a way of testing this!
Once I get the next release out, I'll spend some time on this issue.
In the meantime one thing that helps is to use the option --threads 1
since it slows down the number of requests.
Looks like I fixed it. I'd forgotten to put 429 in the list of errors to do backoff for. Simple fix.
https://github.com/gilesknap/gphotos-sync/runs/6476970287?check_suite_focus=true
@synman @qrkourier Please can you try the HEAD of main to see if it works for your usescase?
Thanks
OK closing as fixed.
Describe the bug I'm unable to re-sync to download my newer photos despite having successfully done some in prior years. The search API is responding with a backoff error, and the 429-response branch isn't quite addressing this particular issue. I plan to work on the problem in my fork and to track progress and gather feedback here.
To Reproduce