-
Notifications
You must be signed in to change notification settings - Fork 118
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
server.close() does not work?? #99
Comments
Sorry, It's actually server.stop(), but that doesn't really matter since that one does not work either :) |
@Foxhoundn Thanks for finding this. Let me dig into it and see what is happening |
Because I don't have access to your store/actions its going to be hard for me to debug. Are you able to create a simpler example of this bug without hitting a store? |
In the meantime I found that force a new connection avoid this issue. But if one test fail all the following tests will trigger this
Is it possible that the problem is due to reconnection activated by default? |
I'm having a similar "already listening" problem, and I tried
and first typescript said those weren't valid keys, and when I |
I'm also getting this error when I attempt multiple vitest cases, both concurrent and non-concurrent |
@spacehash Can you please provide a minimal reproducible test case? |
In my case it was a sign of a bug in my code/test which was causing it not to reach the |
The text was updated successfully, but these errors were encountered: