-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
src: write named pipe info in diagnostic report #38637
Conversation
6c0cadd
to
6ae29a1
Compare
Writes pipe handles with `uv_pipe_getsockname()` and `uv_pipe_getpeername()`.
6ae29a1
to
534db1a
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Just set up a windows environment to test around the test suite compatibility issue. I will update once the test gets fixed. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@addaleax @gireeshpunathil @richardlau updated to pass windows tests. PTAL :) |
LGTM! |
// Exit on loss of parent process | ||
const exit = () => process.exit(2); | ||
process.on('disconnect', exit); | ||
function pipeName(windowsExtended) { |
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.
This function is only called with windowsExtended
set to true
so the parameter is superfluous?
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.
Updated common.PIPE to use '\\?\' prefix. Most likely there should not be any difference regarding the pipe API. However my local windows VM doesn't behave well and lots of unrelated test cases were falling for unknown reasons. So just pushed the updates and let's see what the CI says.
This comment has been minimized.
This comment has been minimized.
various pipe connect API failed in parallel/test-net-connect-options-path.
This comment has been minimized.
This comment has been minimized.
CI: https://ci.nodejs.org/job/node-test-pull-request/38219/
|
CI: https://ci.nodejs.org/job/node-test-pull-request/38223/
|
CI: https://ci.nodejs.org/job/node-test-pull-request/38229/
|
Landed in 50f076c |
Writes pipe handles with `uv_pipe_getsockname()` and `uv_pipe_getpeername()`. PR-URL: nodejs#38637 Fixes: nodejs#38625 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Writes pipe handles with
uv_pipe_getsockname()
anduv_pipe_getpeername()
.Fixes: #38625