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

Couldn't start client Amazon Q Language Server #6466

Open
naeem-zenkoders opened this issue Jan 30, 2025 · 4 comments
Open

Couldn't start client Amazon Q Language Server #6466

naeem-zenkoders opened this issue Jan 30, 2025 · 4 comments
Labels
amazon-q bug We can reproduce the issue and confirmed it is a bug. codewhisperer lsp needs-response Waiting on reply from issue/PR author. partner-team Triggers issue routing to owner team

Comments

@naeem-zenkoders
Copy link

Problem

starting of extension shows some errors:

2025-01-30 16:18:31.091 [info] LspController: LSP already installed
2025-01-30 16:18:31.467 [info] [Info  - 4:18:31 PM] LSP server starts
2025-01-30 16:18:32.361 [info] [Error - 4:18:32 PM] Server initialization failed.
2025-01-30 16:18:32.361 [info]   Message: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\bin\napi-v3\win32\x64\onnxruntime_binding.node
  Code: -32603 
2025-01-30 16:18:32.363 [info] [Error - 4:18:32 PM] Starting client failed
2025-01-30 16:18:32.363 [info]   Message: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\bin\napi-v3\win32\x64\onnxruntime_binding.node
  Code: -32603 
2025-01-30 16:18:32.364 [error] LspController: LSP failed to activate Error: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\bin\napi-v3\win32\x64\onnxruntime_binding.node
2025-01-30 16:18:32.364 [info] [Error - 4:18:32 PM] Unhandled exception: Cannot access 'ONNX_NODE' before initialization
ReferenceError: Cannot access 'ONNX_NODE' before initialization
    at c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\extension.js:418:23585
2025-01-30 16:23:25.617 [info] telemetry: sent batch (size=8)

Steps to reproduce the issue

when starting VS Code IDE.

Expected behavior

should start normally.

System details (run AWS: About and/or Amazon Q: About)

Amazon Q extension

  • OS: Windows 11
  • Visual Studio Code version: 1.96.4
  • AWS Toolkit version:
  • Amazon Q version:
    OS: Windows_NT x64 10.0.26100
    Visual Studio Code extension host: 1.96.4
    Amazon Q: 1.44.0
    node: 20.18.1
    electron: 32.2.6
@naeem-zenkoders naeem-zenkoders added the bug We can reproduce the issue and confirmed it is a bug. label Jan 30, 2025
@jpinkney-aws
Copy link
Contributor

Hi! In your Amazon Q VS Code settings, do you have the "Amazon Q: Workspace Index Use GPU" enabled? Alternatively, do you have "Amazon Q: Workspace Index" enabled? If so, is it possible for you to try turning those off and then restart or reload VS Code? Thank you!

@jpinkney-aws jpinkney-aws added needs-response Waiting on reply from issue/PR author. amazon-q lsp labels Jan 30, 2025
@naeem-zenkoders
Copy link
Author

I have un-checked both "Amazon Q: Workspace Index Use GPU" and "Amazon Q: Workspace Index" and then restarted the VS Code, but still same issue...

@leigaol
Copy link
Contributor

leigaol commented Jan 30, 2025

Hi @naeem-zenkoders ,

Is it possible for you to remove this folder c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver entirely and then restart VS Code?

I was able to reproduce such issue by manually removing the onnxruntime_binding.node. It seems like the operation system removed this .node file for some reason or the download process went wrong at some point. By removing the folder entirely, at the time of extension restarts, the Q extension will download necessary libraries one more time to start the language server.

Seeing such error prompt of LSP not starting will not affect the majority of Amazon Q features.

Feel free to provide more logs for us to triage why the .node file is missing.

Thanks,
Lei

@naeem-zenkoders
Copy link
Author

Thank you so much Lei, I have applied your suggestions and then started VS Code, it was good for a while but soon after the error came again.

Image

@justinmk3 justinmk3 added the partner-team Triggers issue routing to owner team label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amazon-q bug We can reproduce the issue and confirmed it is a bug. codewhisperer lsp needs-response Waiting on reply from issue/PR author. partner-team Triggers issue routing to owner team
Projects
None yet
Development

No branches or pull requests

4 participants