-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
ReadTimeout: HTTPSConnectionPool(host='camping.bcparks.ca', port=443): Read timed out. (read timeout=30) #354
Comments
#355 stacktrace
|
#354 and #355 both seem to indicate that the camping.bcparks.ca API experienced downtime which led to the exceptions. Camply has some exception handling that should allow for some downtime, but if an API is down for long enough then an exception is expected. I will make sure that the GoingToCamp provider is using the same exception handling as other providers to allow for limited API downtime. |
I'd just prefer it keeps hitting the endpoint, and after 10 failures or 20 or something use pushover to notify me its down, and notify me once it comes back after it hits the determined failure. |
Man this is terrible right now. just going to run it in a loop in the shell I guess? |
this change ignores GoingToCamp downtime for up to an hour resolves #354
this change ignores GoingToCamp downtime for up to an hour resolves #354
The text was updated successfully, but these errors were encountered: