fix(go-feature-flag-web): avoid infinite loop in waitWebsocketFinalSt… #1104
Conversation
This file contains hidden or 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
…atus Signed-off-by: Thomas Poignant <[email protected]>
Member
Author
|
Tests are broken, I'll fix them. |
Signed-off-by: Thomas Poignant <[email protected]>
Member
Author
|
@augustinasrce I had to change the approach and based the wait state with a timeout. I will appreciate a new review. |
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.
This PR
This PR fixes the issue thomaspoignant/go-feature-flag#2753 for the web provider when we had an infinite loop when trying to connect with the websocket and an invalid API key.
Related Issues
Fixes thomaspoignant/go-feature-flag#2753