-
-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
Node hangs upon exit when using @Sse and app.enableShutdownHooks() #6643
Comments
Please provide a minimum reproduction repository. |
The code provided is not enough? It is the whole "project". If you do copy/paste to a file and run it, it shows the problem. |
When providing code for a reproduction, especially for a framework, a git repo is usually appreciated |
OK, I really do not get it but this code was honestly hanging in the morning. The same one does not now. Closing. Sorry to bother you. |
And... we're back. The difference between morning and now is that in the morning there were clients connected to the SSE endpoint. I will edit the description and prepare repo. |
Sigh. While preparing the repo I wrote simple client in vanilla javascript and in that one it works as expected as opposed to when our Angular client is connected. Therefore, closing again 😃 |
Bug Report
Current behavior
When annotating route with
@Sse('tada')
and usingapp.enableShutdownHooks();
and there are clients connected to the SSE endpoint the process does not exit when SIGINT (or possibly other) request to terminate is received.One must press
Ctrl+C
twice to terminate. Or click Stop button in Webstorm twice.When there are no clients connected to the endpoint the process is terminated correctly.
Input Code
Expected behavior
App terminates when asked to.
Possible Solution
IDK
Environment
Oh, and thx for Nest.
The text was updated successfully, but these errors were encountered: