Yassin Kortam 2310daef7e fix(proxy-extras): run prisma migrate deploy under the pinned coordinator lock instead of Prisma's session advisory lock (#46368) ... Through a transaction-mode pooler Prisma takes pg_advisory_lock(72707369) on one backend and releases it on another, so the first backend keeps the lock while idle and the next boot waits on it. Migrations now run with PRISMA_SCHEMA_DISABLE_ADVISORY_LOCK=1 while LiteLLM holds the coordinator lock and Prisma's key as transaction-level locks on one pinned connection, so nothing can outlive the migration Resolves LIT-9571 Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>		2026-10-14 15:10:27 -07:00
..
__init__.py	ci: move caching, proxy-extras, gateway and enterprise tests into tests/unit and run them from litellm-tests (#42902)	2026-09-24 15:49:59 -07:00
test_litellm_proxy_extras_logging.py	ci: move caching, proxy-extras, gateway and enterprise tests into tests/unit and run them from litellm-tests (#42902)	2026-09-24 15:49:59 -07:00
test_litellm_proxy_extras_utils.py	fix(proxy-extras): run prisma migrate deploy under the pinned coordinator lock instead of Prisma's session advisory lock (#46368)	2026-10-14 15:10:27 -07:00
test_prisma_toolchain.py	test: migrate proxy security, schema migration and MCP legacy tests (#45937)	2026-10-11 16:17:24 -07:00
test_request_log_indexes.py	fix(proxy-extras): build the SpendLogs indexes in the migration job instead of in migrations (#43948)	2026-10-01 14:12:22 -07:00