Skip to content
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 #420 #173

Open
manuelnagele opened this issue Jun 1, 2014 · 7 comments
Open

Error #420 #173

manuelnagele opened this issue Jun 1, 2014 · 7 comments

Comments

@manuelnagele
Copy link

As of today I keep getting this Error. Any Ideas?

@Vistaus
Copy link

Vistaus commented Jun 8, 2014

Same here. Was just trying it out because I've never used earthquake before but because of this error it's unusable.

@bascht
Copy link

bascht commented Jun 11, 2014

@manuelnagele might be the same as I got in #171.

@manuelnagele
Copy link
Author

@bascht For me it keeps reconnecting once the error pops up. I have tried re-authenticating, reinstalled the gem (+dependencies) and ruby.

@bascht
Copy link

bascht commented Jun 12, 2014

@manuelnagele yep. Same here. :-/

@noisufnoc
Copy link

from Twitter's API Docs:

420 Enhance Your Calm
Returned by the version 1 Search and Trends APIs when you are being rate limited.

Is there anyway to configure a backoff to handle being rate limited?

@GPif
Copy link

GPif commented Dec 20, 2014

It seems that, by default, it try to reconnect every 30, also according to the twitter docmentation, it send an "alive" beacon every 30 second too. To many reconnection provoke the 420 error which pend the connection for 1 minute, then 2, then 4 etc ...
We can raise the delay before a reconnection in the config file with:
Earthquake.config[:no_data_timeout] = 125

I put 125 for more than 2 minute so even if we have 2 420 error there is still a chance.

@GPif
Copy link

GPif commented Dec 20, 2014

In the end it seems that the issue comme from the Twitter library used. It is outdated, there is no update for years and twitter politics with API has change. I am afraid that there is nothing that can be done unless a big update of the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants