fix: add process-level uncaughtException and unhandledRejection handlers#124
Conversation
The application had SIGTERM/SIGINT handlers but no handlers for uncaught exceptions or unhandled promise rejections, causing silent crashes without logging or cleanup. Both handlers now log the error and call the existing shutdown() function for graceful cleanup (Sentry flush, WS close, HTTP server close) with the existing 10s force-exit timeout as a safety net. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 24 minutes and 20 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Sentinel security review — MERGE Without No blocking findings. Security APPROVED. |
Summary
uncaughtExceptionorunhandledRejection, causing silent crashes without logging or cleanupshutdown()function, which handles Sentry flush, WebSocket cleanup, HTTP server close, and has a 10s force-exit timeoutFiles Changed
src/index.ts— Added 2 process event handlers (8 lines)Test plan
tsc --noEmit)🤖 Generated with Claude Code