5c92c2a0e9
Auto-resume bug: kn and nspd_geo resume-on-worker_ready required heartbeat >5min / >10min stale. After redeploy worker boots in ~1-2 min, so jobs killed seconds before deploy had fresh heartbeat and were NEVER auto-resumed — required manual cancel + resume. Fix: drop time threshold entirely. On worker_ready ANY 'running' or 'paused' job is by definition a zombie (no worker exists yet), safe to resume all of them. Concurrency bump: 5 -> 8 prefork slots. Headroom for 5 geo jobs + 1 kn sweep + 2 objective tasks running simultaneously. Each slot ~150MB RSS -> ~1.2GB total, well within 6GB VPS RAM budget. |
||
|---|---|---|
| .. | ||
| alembic | ||
| app | ||
| db/init | ||
| output | ||
| tests | ||
| .dockerignore | ||
| .env.example | ||
| .env.runtime.example | ||
| alembic.ini | ||
| debug.log | ||
| Dockerfile | ||
| pyproject.toml | ||
| uv.lock | ||