aws / aws/aws-toolkit-vscode

Amazon Q Language Server fails to start: "LSP failed to activate... initialize failed... The specified module could not be found."

Open
#6,466 6 comments 0 reactions 0 assignees View on GitHub
amazon-q bug codewhisperer lsp partner-team
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

## 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

Contributor guide

Open the contributing guide

Research direction

Reproduce startup on Windows 11 with VS Code 1.96.4 and Amazon Q 1.44.0, then inspect the LspController failure and the bundled resources/qserver/dist/bin/napi-v3/win32/x64/onnxruntime_binding.node path reported in the log. Check the extension.js location where ONNX_NODE is referenced; done means the language server activates without the missing-module or initialization errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.