This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
cluster: Sending handle from child to parent fails. #4669
Comments
|
Fix is ready, we'll push it in as soon as possible. |
indutny
added a commit
to indutny/node
that referenced
this issue
Jan 28, 2013
TCPWrap::Initialize() and PipeWrap::Initialize() should be called before any data will be read from received socket. But, because of lazy initialization of these bindings, Initialize() method isn't called. Init bindings manually upon socket receiving. See nodejs#4669
indutny
added a commit
that referenced
this issue
Jan 28, 2013
TCPWrap::Initialize() and PipeWrap::Initialize() should be called before any data will be read from received socket. But, because of lazy initialization of these bindings, Initialize() method isn't called. Init bindings manually upon socket receiving. See #4669
|
Fixed in 0d7a021. Thank you for reporting. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sending a handle from a child process to a parent via
process.send(..., sendHandle)fails with an assertionnode: ../src/tcp_wrap.cc:77: static v8::Local<v8::Object> node::TCPWrap::Instantiate(): Assertion tcpConstructor.IsEmpty() == false' failed.I can reproduce on master at time of writing (0972acb) with this gist: https://gist.github.com/4649770
The relevant pull request that introduced this feature is #2772
The text was updated successfully, but these errors were encountered: