Add graceful shutdown handler for Prisma and HTTP connections #370
Labels
No labels
agent-task
agent-task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pook/compliancebot#370
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add SIGTERM and SIGINT handlers that: (1) call server.close() to stop new connections, (2) set a 10-second force-exit timeout, (3) call prisma.$disconnect() to release the connection pool, (4) log each step with timestamp, (5) process.exit(0) on clean shutdown or process.exit(1) on timeout. This is critical for containerized deployments where pods are killed and restarted. Acceptance: SIGTERM on a running server logs the shutdown sequence and exits within 10 seconds with code 0.
Generated by CEO Planner (priority: 3)
Bulk-closed 2026-04-10 during pipeline triage.
Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch
agent/dispatch/*because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.What to do next:
This issue was superseded, not abandoned. Reopen if still relevant after PR triage.