-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
"Server is throttling, let's slow down a bit." #2386
Comments
Seems to be caused by #2357 as far as I can tell. |
I knew I shouldn't have put that log line ! That's no problem, just add |
and if that doesn't work, just comment the line |
Workaround confirmed, thanks :) |
Spoke too soon. Still getting the error more often than I should.
|
I'm getting this too, one commit ago it seemed to work perfect. Reverting back untill this commit is fixed. |
Ya did git pull when I got on today, getting the same issue |
PR #2388 submitted to resolve. |
Why is it throttling that much anyway? |
@marco208 That's Niantic's rate limiting...the problem isn't the throttle, especially now that MoveToFort is remembering what fort it was last moving past; the problem was honestly just the noise. |
Some people on the forums are reporting that Niantic has increased the throttled from 5s to 10s that's why you might see it that often. |
Shouldn't we be more careful with hamering on the rate limiter? |
You're on the [dev] branch -- careful is for [master] :) |
That doesn't mean we shouldn't make the wait between actions adaptive to the amount of throttling the remote server gives us |
Closing due to #2393 |
Expected Behavior
Should not see this error very often.
Actual Behavior
Steps to Reproduce
Unknown -- potentially just running bot on this commit
Other Information
OS: Ubuntu 14.04.4 LTS
Git Commit: bdf2e7d
Python Version: Python 2.7.6
The text was updated successfully, but these errors were encountered: