Fixed: Reject overflowing Content-Length in webfetch#40
Conversation
Fail fast on 32-bit overflow in blocking and tokio paths.
|
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 |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #40 +/- ##
==========================================
- Coverage 75.10% 74.91% -0.19%
==========================================
Files 67 67
Lines 1976 1985 +9
==========================================
+ Hits 1484 1487 +3
- Misses 492 498 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Fixed: Reject overflowing Content-Length in webfetch
Summary
Content-Lengthexceeds platformusizein both blocking and tokio webfetch.