samm81 0d741022a9 http: add rate limiting (mainly for google) ... - google calendar uses the `403` and `429` codes to perform rate limiting [1][2]. this pr adds `tenacity` to perform exponential back off as suggested in google calendar's docs [3]. [1]: https://developers.google.com/workspace/calendar/api/guides/errors#403_rate_limit_exceeded [2]: https://developers.google.com/workspace/calendar/api/guides/errors#429_too_many_requests [3]: https://developers.google.com/workspace/calendar/api/guides/quota#backoff		2025-09-12 16:20:44 +07:00
..
storage	http: add rate limiting (mainly for google)	2025-09-12 16:20:44 +07:00
system	Apply auto-fixes for RUF rule	2025-08-29 10:17:44 +02:00
unit	http: add rate limiting (mainly for google)	2025-09-12 16:20:44 +07:00
__init__.py	Update deprecated usages of hypothesis	2024-12-09 01:30:44 +01:00
conftest.py	Remove references to obsolete event_loop fixture	2025-08-25 17:12:21 +02:00