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

Failed to load library libonnxruntime_providers_cuda.so with error: libonnxruntime_providers_cuda.so: cannot open shared object file: No such file or directory #5868

Open
willmakley opened this issue Oct 25, 2024 · 3 comments
Labels
amazonq bug We can reproduce the issue and confirmed it is a bug. lsp needs-response Waiting on reply from issue/PR author.

Comments

@willmakley
Copy link

Problem

On opening a Ruby on Rails project in VSCode, Amazon Q Language Server shows the following error:

Request initialize failed with message: /onnxruntime_src/onnxruntime/core/session/provider_bridge_ort.cc:1637 onnxruntime::Provider& onnxruntime::ProviderLibrary::Get() [ONNXRuntimeError] : 1 : FAIL : Failed to load library libonnxruntime_providers_cuda.so with error: libonnxruntime_providers_cuda.so: cannot open shared object file: No such file or directory

Steps to reproduce the issue

Open a project in VSCode

Expected behavior

No error.

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

  • OS: Ubuntu 24 running on WSL 2, all latest updates
  • Visual Studio Code version: 1.94.2
  • AWS Toolkit version: N/A
  • Amazon Q version: 1.30.0 (I think) last updated 2024-10-22, 10:49:44
@willmakley willmakley added the bug We can reproduce the issue and confirmed it is a bug. label Oct 25, 2024
@leigaol
Copy link
Contributor

leigaol commented Oct 25, 2024

Hi @willmakley , in your Amazon Q VS Code settings, do you have the Amazon Q: Workspace Index Use GPU enabled? If so, is it possible for you to turn it off and then restart or reload VS Code? Thank you!

@justinmk3 justinmk3 added the needs-response Waiting on reply from issue/PR author. label Oct 25, 2024
@willmakley
Copy link
Author

Yes, it was on (by default) and turning it off does seem to have resolved the issue.

@leigaol
Copy link
Contributor

leigaol commented Oct 25, 2024

On by default is not expected. In our configuration, we make it off by default.

You are seeing this error because CUDA driver was not ready in the Ubuntu environment. If there is a valid CUDA installed, the error should go away.

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. lsp needs-response Waiting on reply from issue/PR author.
Projects
None yet
Development

No branches or pull requests

4 participants