-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve error message for invalid response lengths #2862
Improve error message for invalid response lengths #2862
Conversation
WalkthroughThe recent update enhances the error handling within the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- lightning-block-sync/src/http.rs (1 hunks)
Additional comments: 1
lightning-block-sync/src/http.rs (1)
- 291-291: The error message for invalid response length has been improved to include the actual length, enhancing clarity for debugging. This change aligns with the PR's objective to provide more specific error messages.
d3ad5ac
to
bb9b389
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- lightning-block-sync/src/http.rs (2 hunks)
Files skipped from review as they are similar to previous changes (1)
- lightning-block-sync/src/http.rs
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #2862 +/- ##
==========================================
- Coverage 89.18% 89.18% -0.01%
==========================================
Files 116 116
Lines 93098 93098
Branches 93098 93098
==========================================
- Hits 83034 83028 -6
- Misses 7538 7540 +2
- Partials 2526 2530 +4 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, just an error message change and is, indeed, a bit cleaner.
Presently, HTTP response bodies of length 0 or exceeding
2 * 4_000_000 + 32_000
simply return a spuriousout of range
error.This uses less confusing phrasing.