fix(receiver): Reconnect websocket if receiving errors out #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 21, 2024
kalbasit
force-pushed
the
server-should-start-receive-loop
branch
2 times, most recently
from
5462eb5 to
dd65e22
Compare
kalbasit
force-pushed
the
reconnect-on-errors
branch
from
22ebc65 to
ca2a98e
Compare
kalbasit
changed the base branch from
server-should-start-receive-loop
to
graphite-base/20
kalbasit
force-pushed
the
graphite-base/20
branch
from
dd65e22 to
dbf7877
Compare
kalbasit
force-pushed
the
reconnect-on-errors
branch
from
ca2a98e to
bb2e063
Compare
ref #8 Co-authored-by: Mathias Fredriksson <[email protected]>
kalbasit
force-pushed
the
reconnect-on-errors
branch
from
bb2e063 to
d4ac8fe
Compare
Merge activity
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds automatic reconnection to Signal API when connection is lost
The client now attempts to reconnect to the Signal API when the connection drops, with a 1-second delay between retries. The websocket connection is now properly managed through a dedicated Connect() method.
ref #8
Co-authored-by: Mathias Fredriksson [email protected]