-
-
Notifications
You must be signed in to change notification settings - Fork 616
Client (or sync) wont stop, even with .stopClient() #2472
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
Comments
This is not possible with the current request interface, blocked on #801 |
I tracked this down to 2 specific timeouts: matrix-js-sdk/src/crypto/index.ts Lines 2037 to 2040 in 858155e
and matrix-js-sdk/src/http-api/utils.ts Lines 26 to 28 in 858155e
As a workaround you can use pnpm patch to patch this package. Specifically in node, timers have an unref() method that tells node that its ok to end the process if the timer is still running. I patched both of these setTimeout(....).unref(); and that allowed node to exit immediately after calling the |
I am writing some Jest based integration tests and ran into this issue:
Temporary workaround for anyone using Jest is to run it with the
|
Hello,
I am trying to use this module to send a notification at the end of a script. It works, except that the client only stops several minutes after calling the
.stopClient()
function. So my program is still awake during this time.The program blocks after
And finally after many minutes I get
Sync no longer running: exiting
and the program finally stops.How can I force the client (and the synchronization) to stop immediately?
Here is the code i'm using:
Full logs
The text was updated successfully, but these errors were encountered: