feat: add configurable request timeout - #22
Conversation
|
Warning Review limit reached
More reviews will be available in 18 minutes and 12 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ 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 |
Summary
request_timeoutconstructor option for controller HTTP requests.None, preserving requests' existing no-timeout behavior unless users opt in.Test Plan
ruff check .pytest -qpython -m buildtwine check dist/*sphinx-build -E -W -b html docs docs/_build/htmlgit diff --checkNotes
This is the next small runtime-safety PR after API-level error handling. It avoids changing default behavior while giving users a power/safety knob to prevent indefinitely hanging controller calls.