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

amazon q "explain" get stuck, logs show "Invalid request body" #4810

Closed
justinmk3 opened this issue Apr 24, 2024 · 2 comments
Closed

amazon q "explain" get stuck, logs show "Invalid request body" #4810

justinmk3 opened this issue Apr 24, 2024 · 2 comments
Labels
amazonq bug We can reproduce the issue and confirmed it is a bug. pending-release

Comments

@justinmk3
Copy link
Contributor

Problem

image

Steps to reproduce the issue

  1. login to Q with personal builder id
  2. select code
  3. right click > send to q > explain
  4. Q chat shows "generating..." and never finishes
  5. logs show [error] Batch error: BadRequestException: Invalid request body

System details (run the AWS: About Toolkit command)

  • OS: macos
  • Visual Studio Code version:
  • AWS Toolkit version: e88e482
@justinmk3 justinmk3 added bug We can reproduce the issue and confirmed it is a bug. amazonq pending-release labels Apr 24, 2024
@justinmk3
Copy link
Contributor Author

#4876

justinmk3 pushed a commit that referenced this issue May 7, 2024
Problem
Q chat may hang when processing fragments of ts/js code. The
Tsx.findNames and Tsx.findNamesWithInExtent functions hang (Promise does
not resolve). These functions invoke WASM/rust code.

- #4935
- #4810

Solution
Remove uses of Tsx.findNames and Tsx.findNamesWithInExtent.

The fully qualified names (FQN) library is used to help service build
prompts with variable names in user's IDE to reduce hallucinations, but
they are not required for normal functionality.
@justinmk3
Copy link
Contributor Author

Resolved by #4954 .

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. pending-release
Projects
None yet
Development

No branches or pull requests

1 participant