-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
http: use listenerCount when adding noop event #46769
Merged
nodejs-github-bot
merged 5 commits into
nodejs:main
from
ShogunPanda:noop-with-haslistener
Mar 8, 2023
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
56693fe
http: use listenerCount when adding noop event
ShogunPanda ff212f7
http: also warn the user when preventing the leak
ShogunPanda 196ec78
net: fix error message
ShogunPanda de99a80
http: remove useless test
ShogunPanda e9b3a8d
http: linted code
ShogunPanda File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
// Flags: --no-warnings | ||
|
||
'use strict'; | ||
|
||
const common = require('../common'); | ||
const assert = require('assert'); | ||
const http = require('http'); | ||
const net = require('net'); | ||
|
||
// This test sends an invalid character to a HTTP server and purposely | ||
// does not handle clientError (even if it sets an event handler). | ||
// | ||
// The idea is to let the server emit multiple errors on the socket, | ||
// mostly due to parsing error, and make sure they don't result | ||
// in leaking event listeners. | ||
|
||
{ | ||
let i = 0; | ||
let socket; | ||
process.on('warning', common.mustCall()); | ||
|
||
const server = http.createServer(common.mustNotCall()); | ||
|
||
server.on('clientError', common.mustCallAtLeast((err) => { | ||
assert.strictEqual(err.code, 'HPE_INVALID_METHOD'); | ||
assert.strictEqual(err.rawPacket.toString(), '*'); | ||
|
||
if (i === 20) { | ||
socket.end(); | ||
} else { | ||
socket.write('*'); | ||
i++; | ||
} | ||
}, 1)); | ||
|
||
server.listen(0, () => { | ||
socket = net.createConnection({ port: server.address().port }); | ||
|
||
socket.on('connect', () => { | ||
socket.write('*'); | ||
}); | ||
|
||
socket.on('close', () => { | ||
server.close(); | ||
}); | ||
}); | ||
} | ||
|
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.
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.
According to @dougwilson the leak warning is emitted also without adding a listener for the
'clientError'
event so this is even more misleading than the original leak warning.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.
I don't understand how is it possible, a repro would be useful.