mirror of
https://github.com/johannesjo/super-productivity.git
synced 2026-07-18 00:46:45 +00:00
5ed1f2c5d0
A timed-out `docker compose run` in deploy.sh SIGTERMs the compose CLI but can leave the migrator container (and its DB connection) running detached, which keeps Prisma's session-level migration advisory lock held and wedges the next deploy with P1002. - deploy.sh: run_migrator() names each one-off migrator container from a single MIGRATOR_NAME_PREFIX and force-removes it (inline + $$-scoped EXIT sweep) so a timed-out run can't orphan it and leak the lock; add timeout -k. - migrate-deploy.sh: recognize P1002 advisory-lock timeouts and print copy-paste diagnosis + cleanup guidance instead of a generic exit 1; never auto-terminate a backend (an active CONCURRENTLY build legitimately holds it). - tests: P1002 fake-npx case + non-vacuous recovery test; assert the name/sweep-filter prefix single-source-of-truth invariant. - env.example: document the recommended higher MIGRATION_TIMEOUT and the new force-remove-on-timeout behavior. |
||
|---|---|---|
| .. | ||
| analyze-storage.ts | ||
| backup.sh | ||
| build-and-push.sh | ||
| clear-data.ts | ||
| delete-user.ts | ||
| deploy.sh | ||
| docker-monitor.sh | ||
| health-alert.sh | ||
| migrate-deploy.sh | ||
| migrate-payload-bytes.ts | ||
| monitor.ts | ||
| MONITORING-README.md | ||
| recover-user.ts | ||
| run-all-monitoring.ts | ||