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
replicateWithWebsocketServer prints endless connection errors although state is canceled #5900
Comments
I see that in 15.7.0 |
My fix is to make the master...koh-osug:rxdb:master#diff-8395abd4c40a2116444ebd5daf4c5f307401693b498faa62513decf879ee2c9f Now I can close the socket manually and the replication client can be terminated. |
The socket should stop retrying the connection when there is no more active replication state. Please make a PR. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. If you still have a problem, make a PR with a test case or to prove that you have tried to fix the problem. Notice that only bugs in the rxdb premium plugins are ensured to be fixed by the maintainer. Everything else is expected to be fixed by the community, likely you must fix it by yourself. |
In my error logic I want to stop the replication and use the
cancel
function of theRxReplicationState
. The implementation still continuously prints:Although the server on the other end is terminated and will also never be started again in my case this error is printed forever.
How to stop the replication attempts and close the web socket behind?
This is my code to connect a client to the replication server:
The cancel function should also disconnect from the server or the
RxReplicationState
should allow to close the web socket.The text was updated successfully, but these errors were encountered: