-
Notifications
You must be signed in to change notification settings - Fork 0
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
If a calendar is deleted, the bot gets stuck in a tight retry loop #84
Labels
bug
Something isn't working
Comments
Another calendar was deleted out from under the bot today, causing another outage.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For this outage, service was halted at 2019-12-13 20:00:04 and restored at 2019-12-14 11:15:42 Pacific time.
According to https://console.cloud.google.com/apis/dashboard, the bot has used 488,717 Google Calendar API calls (99% error rate) in the past 1 day and 499,042 (97% error rate) in the past 30; it's been averaging a little over 9 requests per second.
This is actually strictly a bug in metabot.calendars.google, not metabot proper:
The bare except needs to actually hold onto the exception and check if its code is 404 (or potentially 403, or any non-500) and behave differently (for now, probably log the exception but otherwise just treat it as a successful
.list()
with no results).The text was updated successfully, but these errors were encountered: