fix(chat): Resend auth token on server restart #7156
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.
Problem:
When the server restarted due to a crash, the auth token was not sent again. This caused users to run in to the state where if it crashed and restarted, when they sent a subsequent chat message they'd get stuck with the server asking the user to Authenticate.
Note that server restart is triggered automatically by the LanguageClient, I think.
Solution:
Detect when the server is restarted and manually resend the bearer token again.
Note, this solution needs to be revisited since there may be other initialization logic that needs to run on server restart, aside from just the bearer token.
Repro Steps:
File>New Windowlist all files in {folder}Connection to server got closed. Server will restart.Authenticateagainfeature/xbranches will not be squash-merged at release time.