Skip to content

fix(amazonq): ChatCommunicationManager blocks messages to UI until ready #5697

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
May 9, 2025

Conversation

samgst-amazon
Copy link
Contributor

@samgst-amazon samgst-amazon commented May 8, 2025

sendContextCommands pulls in changes required for the context selection/provider prompts. The server makes this call as soon as it gets the config. There may be situations where context calls are made before we can display them in the browser.

Messages received by the client are sent to the browser through the chat manager and blocked until the ui is ready.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Description

Checklist

  • My code follows the code style of this project
  • I have added tests to cover my changes
  • A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

@samgst-amazon samgst-amazon requested review from a team as code owners May 8, 2025 19:35
Copy link

github-actions bot commented May 8, 2025

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

 Conflicts:
	plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/AmazonQLanguageClientImpl.kt
	plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/model/aws/chat/FlareChatCommands.kt
@samgst-amazon samgst-amazon changed the title fix(amazonq): sendContextCommands queued until chat UI ready fix(amazonq): ChatCommunicationManager handles UI ready state May 8, 2025
@samgst-amazon samgst-amazon changed the title fix(amazonq): ChatCommunicationManager handles UI ready state fix(amazonq): ChatCommunicationManager blocks messages to UI until ready May 8, 2025
rli and others added 2 commits May 8, 2025 15:09
…into samgst/q-lsp-chat-queue-SendContextCommand

# Conflicts:
#	plugins/amazonq/chat/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/webview/Browser.kt
#	plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/flareChat/ChatCommunicationManager.kt
Base automatically changed from rli/post-refactor to feature/q-lsp-chat May 9, 2025 01:04
rli and others added 3 commits May 8, 2025 18:11
…q-lsp-chat-queue-SendContextCommand

 Conflicts:
	plugins/amazonq/chat/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/webview/BrowserConnector.kt
	plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/AmazonQLanguageClientImpl.kt
	plugins/amazonq/shared/jetbrains-community/src/software/aws/toolkits/jetbrains/services/amazonq/lsp/flareChat/ChatCommunicationManager.kt
@rli rli merged commit 9b4d638 into feature/q-lsp-chat May 9, 2025
13 of 16 checks passed
@rli rli deleted the samgst/q-lsp-chat-queue-SendContextCommand branch May 9, 2025 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants