-
Notifications
You must be signed in to change notification settings - Fork 231
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
Releasing write() callbacks on error #133
Comments
I am ok to submit a PR on this issue, if you think this should be addressed. |
Or should I resubmit this into the iojs repo? |
Closing and resubmitting to iojs, as it might be the best place to address this anyway. |
I wanted something like this in node, but for some reason the issue was closed by @chrisdickinson. See nodejs/node-v0.x-archive#5920. |
I reposted on iojs: nodejs/node#1746 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In case the streams errors, e.g. for a broken TCP socket, or an application error, all buffered write callbacks are never called, here is an example:
The actual code I am using to fix this behavior is https://github.com/mcollina/aedes/blob/master/lib/client.js#L87-L91.
I spoke to @mafintosh about this one at a couple of conference, so better log it here (and maybe resolve it).
The text was updated successfully, but these errors were encountered: