-
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
Wrapping existing net.Socket does not work #37873
Comments
I don't think you need to wrap with |
I'm aware that |
Hi, Sorry. I'm just aware that the expected behavior section is missing. Could you provide what you are expecting from the snippet? |
Sure. What I was expecting is that the |
I will adapt my code to use
In my view |
Sure, I agree with you that the part of document needs improve if it leads misuse. Would you interest in opening a PR to correct that? |
I also need help to understand the exact meaning of words in document.
Since wrapping an existing socket seems throwing error here, what type of existing socket can be passed here? cc @nodejs/net |
Error is thrown from Libuv, code is as follow.
related: |
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
No required condition (as far as I can tell).
What is the expected behavior?
That a new
net.Socket
instance is created which behaves exactly like the original instance (c
in this case).What do you see instead?
An error is thrown (EEXISTS):
Additional information
The text was updated successfully, but these errors were encountered: