yuneng-jiang d41e5e29ce Extract _deploy_with_idempotent_resolution loop for P3009/P3018 ... The previous approach resolved one idempotent migration per outer retry attempt, exhausting all 5 retries when a DB had 4+ idempotent failures (e.g., tables/columns already created by the old force-apply logic). Now _deploy_with_idempotent_resolution loops internally: deploy → detect idempotent P3009/P3018 → rollback + resolve → re-deploy, until all idempotent migrations are resolved or a non-recoverable error is hit. This keeps outer retries available for transient errors (timeouts, etc). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-12 11:29:42 -07:00
..
test_litellm_proxy_extras_utils.py	Extract _deploy_with_idempotent_resolution loop for P3009/P3018	2026-03-12 11:29:42 -07:00