GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — http: https requestTimeout 0 by ronag · Pull Request #35264 · nodejs/node Conversation
|
|
Review requested:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Fast track? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
lgtm
my bad! +1 to fast-track
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@nodejs/build this should hit v14 as soon as possible. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| client.write('12345678901234567890\r\n\r\n'); | ||
| }, common.platformTimeout(2000)).unref(); | ||
|
|
||
| const errOrEnd = common.mustCall(function(err) { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
| const errOrEnd = common.mustCall(function(err) { | |
| const errOrEnd = common.mustCall(function() { |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| }); | ||
| let response = ''; | ||
|
|
||
| client.on('data', common.mustCall((chunk) => { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
How can you be sure that this is called only once?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| setTimeout(() => { | ||
| client.write('12345678901234567890\r\n\r\n'); | ||
| }, common.platformTimeout(2000)).unref(); |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
| setTimeout(() => { | |
| client.write('12345678901234567890\r\n\r\n'); | |
| }, common.platformTimeout(2000)).unref(); |
This does not seem to be very useful. The other peer already destroyed the socket when this write is attempted so this will result in a guaranteed error, no?
Also shouldn't all the writes be done after the 'connect' event?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| }); | ||
|
|
||
| client.on('end', errOrEnd); | ||
| client.on('error', errOrEnd); |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
| client.on('error', errOrEnd); |
errOrEnd is returned by common.mustCall() so it can only be called once but is used a listener for two different events. This does not seem correct.
Under what circumstances is the 'error' event emitted here? I can only think of connection errors and a write after end error. I think the latter never occurs as the timer that would cause this is unrefed (the process exists before the write on line 60 occurs).
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@lpina: The added test is just a copy paste from an existing test but with http replaced with https. This landed in 753f3b247a. Though we might want to fix those I think that's out of scope of this PR, i.e. I don't think we should stop this PR from fast tracking due to this. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
I disagree. It's a copy paste of an existing test, yes but it's a new test so I see no reason to open a new PR to fix it. We can improve the test without a new PR and still fast track this. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
I see. I don't have the answers to your comments. Sorting them out will probably take a while unless the original author has time. Should I remove most of the test and just add an assertion for the default value instead (which is what this PR is fixing)? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Please do. I'll add a new test and fix the previous one after this land. We need to ship this asap. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Is it ok now @lpinca? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@nodejs/tsc this needs to be fast-tracked. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Luigi Pinca <[email protected]>
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Fixes: #35261 PR-URL: #35264 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Rich Trott <[email protected]>
|
Force-pushed 5461794 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Fixes: #35261 PR-URL: #35264 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Fixes: nodejs#35261 PR-URL: nodejs#35264 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Rich Trott <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Websocket connections incorrectly timing out after 2 minutes in node 14.11? Possible regression
There was an error while loading. Please reload this page.