You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Assertion failed: (uv__stream_fd(stream) >= 0), function uv_read_start, file ../deps/uv/src/unix/stream.c, line 1477. #987
Can you report this to mscdex/node-imap first, please? It might be a bug in that module that flew under the radar until now. If not, @mscdex should holler and I'll reopen the issue. Thanks.
assume that net.Socket is a JSStream if it has yet no _handle (i.e. .connect() wasn't called)
allow adding parent socket handle to TLSSocket after creating it
The first solution is very easy to implement and should generally get various code like that test case working without any problems, except probably reduced bandwidth.
The second one is a bit complicated and might take some time to implement.
Activity
bnoordhuis commentedon Feb 27, 2015
Can you report this to mscdex/node-imap first, please? It might be a bug in that module that flew under the radar until now. If not, @mscdex should holler and I'll reopen the issue. Thanks.
vkurchatkin commentedon Feb 27, 2015
It looks like
node-imapis pure js, so it is probably io.js bugvkurchatkin commentedon Feb 27, 2015
@gnostic do you have a way to reproduce this issue? what you do reverts libuv/libuv@19d3d50
mscdex commentedon Feb 27, 2015
@bnoordhuis As @vkurchatkin said,
imapis pure js, so the error is happening in io.js C++ land.sergenikitin commentedon Mar 1, 2015
io.js v1.4.2 has the same problem.
rvagg commentedon Mar 1, 2015
@sergenikitin are you on Windows? if so, see #1005 and perhaps #1008 is relevant?
sergenikitin commentedon Mar 1, 2015
@rvagg no, OS X 10.10.2
rvagg commentedon Mar 1, 2015
/cc @indutny this looks relevant to your stream changes
indutny commentedon Mar 2, 2015
@gnostic does following patch fix the problem for you?
sergenikitin commentedon Mar 3, 2015
@indutny
I checked this patch, it's not fix the problem. Still have
indutny commentedon Mar 3, 2015
@sergenikitin is there any way to reproduce it?
indutny commentedon Mar 3, 2015
Ok, a test case:
indutny commentedon Mar 3, 2015
@bnoordhuis @vkurchatkin @rvagg I have two solutions:
net.Socketis aJSStreamif it has yet no_handle(i.e..connect()wasn't called)TLSSocketafter creating itThe first solution is very easy to implement and should generally get various code like that test case working without any problems, except probably reduced bandwidth.
The second one is a bit complicated and might take some time to implement.
What do you think about doing (1) and then (2)?
bnoordhuis commentedon Mar 3, 2015
@indutny Is what you are proposing in (1) spiritually equivalent to:
?
tls: accept empty `net.Socket`s
indutny commentedon Mar 3, 2015
@bnoordhuis like this #1046
tls: accept empty `net.Socket`s
deps: libffi: cherry-pick 9ca53a19833d
deps: libffi: cherry-pick 9ca53a19833d
deps: libffi: cherry-pick 9ca53a19833d