Check that socket is still connected before invoking next()
jondubois opened this issue · comments
Right now in MIDDLEWARE_PUBLISH_OUT, because next()
is called asynchronously, it's possible that it might be invoked after the socket has become disconnected in - So maybe there should be an additional check on socket.state
to make sure that it's not disconnected before calling next()
.
that is a good point. Sorry, I've been on vacation and haven't been on github. I'll fix it and push now.
0.2.2 - Fixed. Thanks!