fix(server): handle relay usage callback errors#94
Conversation
|
Warning Review limit reached
More reviews will be available in 25 minutes and 22 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 Plus Run ID: 📒 Files selected for processing (2)
✨ 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
Test plan
bun test tests/unit/sse-line-cap.test.tsbun run typecheckbun run buildbun testbun run release-checkFixes #51
Summary by cubic
Make RelayStream usage callbacks best-effort and non-blocking so they never delay or break streaming. All callback errors (sync, async, non-Error) are caught, normalized, and logged to avoid unhandled rejections.
onUsagenow returnsvoid | Promise<void>and is executed without blocking the stream.Errorbefore logging.Written for commit 73f5ce0. Summary will update on new commits.
Review in cubic