Add more resilience over connectivity issues #79
Merged
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
s6o
pushed a commit
to s6o/phoenix-socket-dart
that referenced
this pull request
May 23, 2024
* add toxiproxy service for testing * add tests for certain connection issues * fixes * fix service name * fix logging flag
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.
Test out socket and channel recovery with respect to different timings of connection drop and TCP peer reset, including assertions around what happens to message sent at different moment around these connectivity issues.
Added toxiproxy service in a docker compose cluster to have tighter control over connectivity with Phoenix Socket backend.