-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
All query's return fail #8
Comments
Checked just now. Working... It will be great if you can mention the time (keep in mind time zone) when this happened. |
thank for the quick response. yes, it is working now ..... the error's happened on 06/15/2022 around 7:25 AM Eastern Daylight Time zone (in New York, NY) thanks for looking into this and maintaining such a good API for free. |
There are one or two exceptions that occur during the period of high rate of requests to the API like in this case. These unhandled exceptions returns a "invalid query" response. But this can be a server side error. The error handling will be improved soon. I am working on some major features, which will be rolled out once most of them are ready. This also includes better error handling. Thanks for informing about the incident. |
hi, // 2022 06/16/ 11:59:26 { |
https://status.heroku.com/incidents/2439 not able to access application logs. |
Still ongoing // 2022/06/16 14:51:25 // https://weatherdbi.herokuapp.com/data/weather/london { "status": "fail", "message": "invalid query", "query": "london", "code": 0, "visit": "https://weatherdbi.herokuapp.com/documentation/v1" } |
happening due traffic spikes.... |
hi,
it seems that a bug or something else has caused your API to always return with "Status" : failed.
examples:
https://weatherdbi.herokuapp.com/data/weather/brooklyn
https://weatherdbi.herokuapp.com/data/weather/miami
{
"status": "fail",
"message": "invalid query",
"query": "brooklyn", // or "miami"
"code": 0,
"visit": "https://weatherdbi.herokuapp.com/documentation/v1"
}
can you please look into this
thank you
The text was updated successfully, but these errors were encountered: