mateo-berri 7b8cc0319e fix(proxy-extras): only spend a migrate-deploy attempt when a pass made no progress ... The v2 migration resolver gave `prisma migrate deploy` four attempts, and every recovery path ended in a bare `continue`, so each one burned an attempt. A database first brought up with `--use_prisma_db_push` has a full schema and no migrations ledger, so the baseline spent attempt one and the first three migrations whose objects already existed spent the rest. The proxy then exited before binding its port, and that database could never be moved onto the resolver. The retry budget now counts only attempts that got nowhere. Creating the baseline, and each migration newly marked applied, leaves the budget alone, so a push-created database works through its pre-existing objects one pass at a time. Timeouts, deadlock rollbacks, advisory-lock waits, and a repeat of a recovery that already ran still spend an attempt, so a run that stops making progress gives up exactly as before.		2026-09-02 23:56:09 -07:00
..
test_litellm_proxy_extras_utils.py	fix(proxy-extras): only spend a migrate-deploy attempt when a pass made no progress	2026-09-02 23:56:09 -07:00