jacobh2
e39ec9a77b
The end-to-end suite had never been run. Its first run failed six ways, all of them the page sitting on the login screen: every browser page load re-obtains an access token, the refresh endpoint allows thirty a minute per address, and a twenty-test run makes about fifty of them from one address. Half came back 429, and a failed refresh is indistinguishable from being logged out. Raising the ceiling would only move it and make a green suite depend on how fast the machine is, so the limiter is switched off for the test backend alone — it measures a client, and the runner is not one. It stays on everywhere else. With that gone, one real failure was left, and it belonged to the commit that claimed to have fixed it: cell widths were held, but a week whose cell carries a holiday name still stood taller than its neighbours, because each week is its own grid and none can see another's height. The weeks now share one grid whose rows are all a single fraction, so the tallest sets the rest and no cell can grow its own row. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ei7gCZzdd751uZtPzb1Pep
18 lines
654 B
Python
18 lines
654 B
Python
"""Shared rate-limiter instance.
|
|
|
|
Lives in its own module so routers can import it without triggering the
|
|
circular import that would occur if they imported from app.main.
|
|
|
|
The limiter keys on the remote address, so it is only meaningful where one
|
|
IP really is one client. `settings.rate_limit_enabled` exists to switch it
|
|
off where that is not true (the E2E suite drives every page load from
|
|
127.0.0.1) — see the comment on that setting in `app/config.py`.
|
|
"""
|
|
|
|
from slowapi import Limiter
|
|
from slowapi.util import get_remote_address
|
|
|
|
from app.config import settings
|
|
|
|
limiter = Limiter(key_func=get_remote_address, enabled=settings.rate_limit_enabled)
|