fix: graceful shutdown on uncaughtException (H8)#90
fix: graceful shutdown on uncaughtException (H8)#900x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
Conversation
Per Node.js docs, uncaughtException means the process is in an undefined state. The previous handler swallowed the exception and continued, risking corrupted in-memory state (half-written maps, broken invariants) while signing financial transactions. Now triggers graceful shutdown instead. Railway's ON_FAILURE restart policy (max 10 retries) will bring the keeper back up cleanly with fresh state. The unhandledRejection handler is unchanged — continuing after unhandled Promise rejections is safe per Node.js design. 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 40 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 |
1 participant
Summary
uncaughtExceptionhandler swallowed the exception and continued executionON_FAILURErestart policy brings the keeper back cleanlyTest plan
🤖 Generated with Claude Code