fix(ux): print error message on SSH/exec exit failures#128
Conversation
Replace silent os.Exit calls with log.Errorf messages before exiting, so users see what failed. Replace log.Fatal with log.Errorf + os.Exit(1) to allow deferred cleanup functions to run.
✅ Deploy Preview for devsydev canceled.
|
|
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 43 minutes and 41 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. 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
log.Errorf) before callingos.Exit, so users see what failed instead of a silent exit.log.Fatal/log.Fatalfwithlog.Errorf+os.Exit(1)to allow deferred cleanup functions (like telemetry flush) to run before the process exits.