fix(amazonq): update Q profile and customizations on language-servers crash restart #7671
+521
−18
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
Investigation revealed that when the language server crashed and automatically restarted, the crash recovery mechanism only sent bearer tokens but failed to send profile configuration, leaving the language server stuck in PENDING_Q_PROFILE state.
Solution
Fixed the incomplete crash recovery mechanism by:
• Enhanced crash recovery handler to send both bearer token AND profile configuration during language server restart
• Added comprehensive logging with context tags ([startup], [crash-recovery]) for future debugging
• Created centralized authentication function to prevent code duplication between startup and crash recovery paths
• Added debug logging to pushConfigUpdate and sendProfileToLsp functions to track configuration values
feature/x
branches will not be squash-merged at release time.