fix(llc): null check on websocket connection #2260
Merged
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.
Submit a pull request
Linear: fixes FLU-142
Github Issue: fixes #2218
CLA
Description of the pull request
We have a null check operator on
connectionCompleter
. This can only benull
if there is a disconnect while fetching a token. Now we return the connectionCompleter future before we go async, so this should never happen anymore.We didn't reproduce it, so it's also hard to test.