Closed BoPeng closed 6 years ago
Looks fine on my end. Maybe the API does not like your IP?
It is working now. According to the source code, the error message is displayed when an AJAX call fails, so it might be something related to network or github API.
Found the reason:
{
"message": "API rate limit exceeded for 143.111.84.121. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
"documentation_url": "https://developer.github.com/v3/#rate-limiting"
}
Okey does your fix distinguish the case when wrong / non-existing URL is given so that no valid information can be extracted? I was thinking the prompt should depend on the exact error message you receive.
It is up to us to ensure there is a ticket open for all blog posts. Then whatever error happens, the new error message provides a way to access related issue directly. The exact error message does not really matter and I was even considering replacing the hard-to-understand "rate limit" explanation with something like "Ohh, github hiccuped, ....".
At least the reason is now known.
I have seen this from time to time and have not figured out why this happens:
@gaow what do you see over there now?