Add process-level uncaught exception and unhandled rejection handlers #391
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#391
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 process.on('uncaughtException') and process.on('unhandledRejection') handlers at the application entry point. Log the error with structured JSON including stack trace, timestamp, and request context if available. For unhandled rejections, log and continue (with monitoring alert). For uncaught exceptions, log and trigger graceful shutdown (close Prisma connections, close HTTP server, then process.exit(1)). This prevents silent crashes and ensures errors are observable in production logs. Reference: contractpilot has equivalent issue #335.
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.