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

Q workspace: Getting GLIBCXX_3.4.30 not found errors #6490

Open
scottschreckengaust opened this issue Feb 3, 2025 · 1 comment
Open

Q workspace: Getting GLIBCXX_3.4.30 not found errors #6490

scottschreckengaust opened this issue Feb 3, 2025 · 1 comment
Labels
amazon-q bug We can reproduce the issue and confirmed it is a bug.

Comments

@scottschreckengaust
Copy link

Problem

Getting error messages from Amazon Q Visual Studio Code extension:

Request initialize failed with message: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by ~/.vscode-server/extensions/amazonwebservices.amazon-q-vscode-1.45.0/resources/qserver/dist/build/Release/faiss-node.node)
Code: -32603

Steps to reproduce the issue

Launch with the extension enabled.

Expected behavior

No error messages

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

  • Visual Studio Code version:
Version: 1.96.4 (Universal)
Commit: cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
Date: 2025-01-16T00:16:19.038Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0
  • Amazon Q version:
OS: Linux arm64 6.1.124-134.200.amzn2023.aarch64
Visual Studio Code extension host:  1.96.4
Amazon Q:  1.45.0
node: 20.18.1
@scottschreckengaust scottschreckengaust added the bug We can reproduce the issue and confirmed it is a bug. label Feb 3, 2025
@justinmk3 justinmk3 changed the title Getting GLIBCXX_3.4.30 not found errors Q workspace: Getting GLIBCXX_3.4.30 not found errors Feb 12, 2025
@justinmk3
Copy link
Contributor

Workaround is to disable Q workspace indexing. Setting id: amazonQ.workspaceIndex

Image

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

No branches or pull requests

2 participants