Skip to content
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

Can't send to Amazon Q any smart action #4577

Open
chenxuanzzy opened this issue Mar 22, 2024 · 1 comment
Open

Can't send to Amazon Q any smart action #4577

chenxuanzzy opened this issue Mar 22, 2024 · 1 comment
Labels
amazonq bug We can reproduce the issue and confirmed it is a bug.

Comments

@chenxuanzzy
Copy link

Problem

I find some prompts can't work about Amazon Q even using the command line or right click
Open the developer tools(command:workbench.action.webview.openDeveloperTools) can see the [amazonwebservices.aws-toolkit-vscode]unreachable ERROR
I can see Aws Toolkit Logs will show some Aws commands that do not respond to anything for me. Using my friend account will have the same problem. Here problem is not for all of prompts, just some of prompts but don't know why.

ERROR
image

SUCCESS
image

Steps to reproduce the issue

  1. open the test.js && open AWS Toolkit logs output panel
  2. input my code
  3. selected all code
  4. right click --> Send to Amazon Q --> click any action (or you can select all codes and click "Explain selected code" on Amazon Q chat)
  5. not work anything
  6. open DeveloperTools will see ERROR

Expected behavior

It might show up resp for me, but it didn't do anything.

System details (run the AWS: About Toolkit command)

OS: Darwin arm64 22.6.0
Visual Studio Code extension host: 1.87.1
AWS Toolkit: 2.16.0
node: 18.17.1
electron: 27.3.2

@chenxuanzzy chenxuanzzy added the bug We can reproduce the issue and confirmed it is a bug. label Mar 22, 2024
@justinmk3
Copy link
Contributor

Can you provide the Toolkit logs (but remove any private info)?

  1. In VSCode settings, ensure that "aws log level" is "debug".
  2. Perform the steps to reproduce the issue.
  3. Use the AWS: View Toolkit Logs command to get the logs.
  4. Remove any private info from the logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amazonq bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants