-
Notifications
You must be signed in to change notification settings - Fork 94
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
Github rate limits requests #85
Comments
Yeah, we should definitely be retrying if there's a clear rate-limit header. Also printing a status update to the user so they don't think the script is just hanging. PR welcome. |
I get completed 3 of 112 issues, and then it just seems to stall. Is that the symptom? |
What are the headers that Github returns when you try to submit the stalled issue? |
I'm not sure where to look, sorry. Is there some trace option I can enable? It shows some JSON on the console, and then just stalls with:
Here's the last issue it showed on the console. I don't think this gives you anything useful, though:
I am going to try again now with MacOS Network Link Conditioner set to 200kbps, 400mSec latency as a crude work-around. |
With the Network Link Conditioner enabled, it is progressing. It is very slow in any case, is that normal? But, hey, it made it to 13! ;) The speed seems variable, sometimes it will do a couple in quick succession. I think I will now chance it without dry run mode... |
It copied 67 of 112 issues before dying on a ConnectionResetError [Errno 54]. I will restart with a skip. This would seem a common issue that should be handled as well. |
I'm running a migration of ~4000 issues currently. On average each issue takes ~4s to complete. I have not experienced any rate limit or connection issues so far (> 2000 issues migrated). |
Maybe GitHub's infra is a bit more robust in the last 5 years... 😁 I'll leave this open for a bit in case someone else sees the 403, as we should ideally handle it properly with a delayed retry. |
Github will return a 403 with a header indicating that a request was rate limited. The migration script can uses this information to more robustly respond under these conditions.
The text was updated successfully, but these errors were encountered: