http: remove unused n arg from IncomingMessage._read#64370
Open
efekrskl wants to merge 1 commit into
Open
Conversation
Collaborator
|
Review requested:
|
Signed-off-by: Efe Karasakal <hi@efe.dev>
5df3874 to
eb01019
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #64370 +/- ##
=======================================
Coverage 90.25% 90.25%
=======================================
Files 741 741
Lines 241165 241157 -8
Branches 45428 45427 -1
=======================================
- Hits 217667 217660 -7
Misses 15069 15069
+ Partials 8429 8428 -1
🚀 New features to boost your workflow:
|
pimterry
approved these changes
Jul 8, 2026
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Something I came across while reading the code. We are on V8 version
14.6and https://bugs.chromium.org/p/v8/issues/detail?id=10201 seems to be long fixedBenchmarks look fine, no regression
node benchmark/compare.js --runs 20 --old /tmp/node-before --new ./out/Release/node --filter incoming_headers http