vdirsyncer/tests/storage
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
..
dav Apply auto-fixes for RUF rule 2025-08-29 10:17:44 +02:00
servers Apply auto-fixes for RUF rule 2025-08-29 10:17:44 +02:00
__init__.py ruff: apply auto-fixes 2025-08-29 10:03:24 +02:00
conftest.py Ensure type annotations are backwards compatible 2023-10-29 16:04:23 +01:00
test_filesystem.py Ensure type annotations are backwards compatible 2023-10-29 16:04:23 +01:00
test_http.py http: add rate limiting (mainly for google) 2025-09-12 16:20:44 +07:00
test_http_with_singlefile.py Simplify some statements 2025-08-29 10:17:44 +02:00
test_memory.py Ensure type annotations are backwards compatible 2023-10-29 16:04:23 +01:00
test_singlefile.py Ensure type annotations are backwards compatible 2023-10-29 16:04:23 +01:00