curo/kite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(06): WR-01 reset auth_limiter between tests to prevent 429 cross-contamination

Browse Source 
Add auth_limiter (IP-level limiter from api.auth) to the reset_rate_limiter
autouse fixture in conftest.py, alongside the existing account_limiter reset.
Prevents spurious 429s when tests call /api/auth/* endpoints in a tight loop.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
curo1305
2026-06-04 23:15:48 +02:00
co-authored by Claude Sonnet 4.6
parent 10970d9557
commit 4a5719311b
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/tests/conftest.py
+6 -3
View File
@@ -161,14 +161,17 @@ async def async_client(db_session: AsyncSession):
def reset_rate_limiter(): def reset_rate_limiter():
"""Reset the in-memory rate limiter storage before each test. """Reset the in-memory rate limiter storage before each test.
The account_limiter is a module-level singleton using MemoryStorage. Resets both account_limiter (per-user) and auth_limiter (IP-level) so
Without this fixture, rate limit counters accumulate across tests in the that tight test loops against /api/auth/* do not accumulate counters and
same process and cause unrelated tests to receive 429 responses. cause spurious 429 failures in later tests.
""" """
from services.rate_limiting import account_limiter from services.rate_limiting import account_limiter
from api.auth import limiter as auth_limiter
account_limiter._storage.reset() account_limiter._storage.reset()
auth_limiter._storage.reset()
yield yield
account_limiter._storage.reset() account_limiter._storage.reset()
auth_limiter._storage.reset()
# ── File fixtures ───────────────────────────────────────────────────────────── # ── File fixtures ─────────────────────────────────────────────────────────────