[codex] Add daemon lifecycle retry and visibility tests#796
Conversation
|
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 59 minutes and 58 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. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
…#796) Co-authored-by: Jwalin Shah <jshah1331@gmail.com>
Summary
Problem
Daemon lifecycle behavior around retry timing and visibility-driven auto-start paths had no focused test coverage, making regressions in reconnect handling harder to catch.
Solution
Add a dedicated
useDaemonLifecycletest file that uses fake timers, mocked daemon health hooks, and real daemon store state to verify retry growth, max-attempt cutoffs, reset behavior, and hidden/visible resume logic.Submission Checklist
Impact
No intended product behavior change. Improves confidence in daemon startup/reconnect behavior on the desktop app.
Related