Conversation
|
Warning Rate limit exceeded
⌛ 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. 📒 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
ProcessIObackpressure handling so writes are not replayed whenstdin.write()returnsfalsewrite() === falseas accepted-by-buffer and pause only subsequent writes untildrainWhy this matters
Node stream semantics guarantee that
write()returningfalsemeans the chunk was accepted and buffered. Re-queueing that same chunk can duplicate protocol frames and cause incorrect request delivery.Validation
npx eslint src/runtime/process-io.ts test/transport.test.tsnpm run typechecknpm test -- test/transport.test.tsnpm test -- test/runtime_node.test.tsCloses #144