groton-school / colorize-schoolcal Goto Github PK

Blindly picking the first user calendar at this line is unsafe. A student, let's call her Alice Groton, both synced in her personal Google calendar as Personal Calendar and renamed the root calendar in her Groton Google account to School Calendar, with the result that getting the [0] calendar resulted in calendar being undefined.

Google has undocumented limits on API usage (because of course they do). Not clear how batch requests are counted, but it seems like as a total of the batched requests. Which, it seems, may expose users to 403 and 429 errors. Google recommends an exponential backoff approach to handling those.

Currently only in the dev branch, but this would allow runs that are longer than the documented 30 second run time for scripts on the CardService (although empirically it's closer to 45 seconds). This would also allow for more elbow room for exponential backoff in #2.

Currently if the Colorize actions time out, they can be safely re-run repeatedly until all items are complete (items with the correct color are skipped in subsequent runs).