Yuneng Jiang 0c73928a6d ci(proxy-mgmt-behavior): await LiteLLM_VerificationTokenView creation in fixture ... Fourth CI run still failed because the proxy's lifespan kicks off ``prisma_client.check_view_exists()`` as a fire-and-forget background task — that task is what creates ``LiteLLM_VerificationTokenView``, the SQL view ``user_api_key_auth`` queries to resolve a token to its user_id / user_role / team. On a fresh Postgres (CI), the first test races the background task. The view doesn't exist when the first auth call runs, the resolver falls through to a degraded path that returns ``user_id=None``, and every matrix test that depends on the seeded actor's identity then fails confusingly with "Got user_id=X, Your ID=None" 403s. Locally the view persists across pytest runs so the race is invisible. Fix: await ``prisma_client.check_view_exists()`` explicitly inside the session ``proxy_app`` fixture, after the lifespan enters but before the fixture yields. Deterministic regardless of whether the underlying DB is fresh (CI) or warm (local).		2026-05-19 22:26:52 -07:00
..
management	ci(proxy-mgmt-behavior): await LiteLLM_VerificationTokenView creation in fixture	2026-05-19 22:26:52 -07:00
__init__.py	test(proxy_behavior): scaffold session-scoped async ASGI client + liveness smoke	2026-05-19 21:21:00 -07:00