Yuneng Jiang 6d207ffa5a ci(proxy-mgmt-behavior): add auth-resolver chain diagnostic ... Six runs and the underlying data (token row, user row, view row) all verified correct in CI, but auth still returns user_id=None. This diagnostic calls the resolver primitives directly: 1. ``prisma.get_data(table_name="combined_view")`` → raw view object 2. ``get_key_object(...)`` → cached/DB UserAPIKeyAuth 3. ``get_user_object(...)`` → LiteLLM_UserTable row 4. ``_is_user_proxy_admin`` / ``_get_user_role`` and prints each intermediate via captured stdout (-s). Whichever step returns None/False in CI is where the chain breaks. Imports come from ``litellm.proxy.auth`` (not management_endpoints), so G3 still passes.		2026-05-20 13:11:29 -07:00
..
management	ci(proxy-mgmt-behavior): add auth-resolver chain diagnostic	2026-05-20 13:11:29 -07:00
__init__.py	test(proxy_behavior): scaffold session-scoped async ASGI client + liveness smoke	2026-05-19 21:21:00 -07:00