-
Notifications
You must be signed in to change notification settings - Fork 30.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
stream: end(callback) does not propagate write after end to callback #33684
Comments
Same problem with |
@ronag can I solve it? |
@zhangwinning sure, go ahead and try |
@zhangwinning Sorry, I never saw your comment and created a draft PR. Let me know if you are still working on this and I'll go ahead and close that. |
@rexagod yes, I still working it. |
No problem. I've closed #33786. Go ahead. |
Properly propagate all write errors throught to end callback. Fixes: nodejs#33684
There's been no further activity or discussion here in years. Is there still more to do here? Should we just document issues and move on or is there is still a relevant bug to fix here? |
The text was updated successfully, but these errors were encountered: