-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
fix: eventstream listen on socket for close/end event #5795
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Performance Report✔️ no performance regression detected Full benchmark results
|
dapplion
approved these changes
Jul 24, 2023
🎉 This PR is included in v1.10.0 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Previous PR #5784 resolved issue #5783 but "hijacking" the response (
res.hijack()
) should not be necessary and it is hard to understand all side-effects this has even though as far as I understand in our case it does not have any (#5784 (comment)).I noticed, that in fastify-sse there is a note about removing event listeners (https://github.com/NodeFactoryIo/fastify-sse-v2#note) and there it adds a listener to socket, not the stream (thanks @mpetrunic for the pointers).
I looked into the timings of this and it seems like socket end event is emitted before stream is closed causing event listeners to be aborted earlier. This avoids a race condition trying to send an event even though stream is already closed causing the header already sent error (#5783).
Description
res.hijack()
Note: It might be sufficient to just listen to socket end event but hard to test all edge cases.