You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2024. It is now read-only.
As per documentation, "After the ping message is sent to the server, the system would return a pong message to the client side."
from my understanding is that the pong respond is not guaranteed yet the client SDK always wait for it and close the connection after timeout
and indeed i lose connection after a period of time
The text was updated successfully, but these errors were encountered:
As per documentation, "After the ping message is sent to the server, the system would return a pong message to the client side." from my understanding is that the pong respond is not guaranteed yet the client SDK always wait for it and close the connection after timeout and indeed i lose connection after a period of time
Do you mean that there is no up-to-date data after running for a period of time?
Are there any other phenomena or characteristics that will facilitate us to reproduce the situation you mentioned?
Due to the current implementation's shortcomings, the handling of heartbeat maintenance is not optimal. We plan to refactor this code in future iterations. Please stay in touch
As per documentation, "After the ping message is sent to the server, the system would return a pong message to the client side."
from my understanding is that the pong respond is not guaranteed yet the client SDK always wait for it and close the connection after timeout
and indeed i lose connection after a period of time
The text was updated successfully, but these errors were encountered: