-
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
Feature Request: include missing pipe info in diagnostic report #38625
Labels
feature request
Issues that request new features to be added to Node.js.
report
Issues and PRs related to process.report.
Comments
mscdex
added
feature request
Issues that request new features to be added to Node.js.
report
Issues and PRs related to process.report.
labels
May 10, 2021
mscdex
changed the title
Feature Request: include missing pipe info in process report
Feature Request: include missing pipe info in diagnostic report
May 10, 2021
foxxyz
pushed a commit
to foxxyz/node
that referenced
this issue
Oct 18, 2021
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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature request
Issues that request new features to be added to Node.js.
report
Issues and PRs related to process.report.
Currently in node diagnostic reports TCP and UDP sockets include the local and remote endpoints (using
uv_*_getsockname()
anduv_*_getpeername()
respectively), however pipes/UNIX sockets do not. I believe it should be possible to provide these same values for pipes/UNIX sockets usinguv_pipe_getsockname()
anduv_pipe_getpeername()
.The text was updated successfully, but these errors were encountered: