VSCode with Dev Containers: Using @Search context provider yields an ENOENT error executing ripgrep
Before submitting your bug report
- [X] I believe this is a bug. I'll try to join the Continue Discord for questions
- [X] I'm not able to find an open issue that reports the same bug
- [X] I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS:Ubuntu 22.04.1 on VMWare Workstation 17.5.2 build-23775571
- Continue:0.9.197 and 0.8.46
- IDE:Visual Studio Code 1.92.1
- Model:
- config.json:
{
"models": [
{
"title": "Codestral 22b",
"provider": "ollama",
"model": "codestral:22b-v0.1-q8_0",
"apiBase": "http://sv-llm.c1.mydomain.net:11434/",
"contextLength": 28672,
"completionOptions": {
"maxTokens": 4096
}
},
{
"title": "Llama 3.1 405B Q4_K_M",
"provider": "llama.cpp",
"model": "Llama 3.1 405B Q4_K_M",
"apiBase": "http://sv-aichan.c1.mydomain.net:8080/",
"contextLength": 122882,
"completionOptions": {
"maxTokens": 8192
}
},
{
"title": "DeepSeek Coder V2 236B Q8_0",
"provider": "llama.cpp",
"model": "DeepSeek Coder V2 236B Q8_0",
"apiBase": "http://sv-aichan.c1.mydomain.net:8082/",
"contextLength": 122882,
"completionOptions": {
"maxTokens": 8192
}
},
{
"title": "Mistral Large 123B 2407 Q8_0",
"provider": "llama.cpp",
"model": "Mistral Large 123B 2407 Q8_0",
"apiBase": "http://sv-aichan.c1.mydomain.net:8081/",
"contextLength": 122882,
"completionOptions": {
"maxTokens": 8192
}
}
],
"customCommands": [
{
"name": "test",
"prompt": "{{{ input }}}\n\nWrite a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
"description": "Write unit tests for highlighted code"
}
],
"tabAutocompleteModel": {
"title": "CodeStral 22b",
"provider": "ollama",
"model": "codestral:22b-v0.1-q8_0",
"apiBase": "http://sv-llm.c1.mydomain.net:11434/",
"contextLength": 28672,
"completionOptions": {
"maxTokens": 2048
}
},
"allowAnonymousTelemetry": true,
"contextProviders": [
{
"name": "code",
"params": {}
},
{
"name": "codebase",
"params": {
"nRetrieve": 1000,
"nFinal": 50,
"useReranking": false
}
},
{
"name": "folder"
},
{
"name": "terminal"
},
{
"name": "folder"
},
{
"name": "search"
},
{
"name": "docs",
"params": {}
}
],
"embeddingsProvider": {
"provider": "ollama",
"model": "nomic-embed-text:latest",
"apiBase": "http://sv-llm.c1.mydomain.net:11434/"
}
}
Description
Attempting to use @Search and I always receive a popup with an identical error message than this one from the developer logs: Error getting context items from search: Error: spawn /home/user/.vscode/extensions/continue.continue-0.9.197-linux-x64/out/node_modules/@vscode/ripgrep/bin/rg ENOENT c @ notificationsAlerts.ts:42
This happens with the latest release version as well as the latest pre-release version. Other context providers such as codebase are working.
The "rg" binary is at the specified path and can be executed.
To reproduce
- Go to the chat window.
- Type @Search.
- Fill in the search term, e.g. "mixin"
- Submit the chat request.
- A popup with the described error appears.
Log output
Error getting context items from search: Error: spawn /home/user/.vscode/extensions/continue.continue-0.9.197-linux-x64/out/node_modules/@vscode/ripgrep/bin/rg ENOENT
c @ notificationsAlerts.ts:42
Did you try out building an arm64 build? I had a similar issue and building that worked.
I have only used the release and pre-release versions from the VSCode extension store.
Removed .continue, removed Continue extension, reinstalled, reconfigured. Same issue. Made sure to add it do devcontainer.json and nothing.
I suspect this is because I'm using Dev Containers.
It appears that rg is executed in the context of the container which is why there the rg executable can not be located.
This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.
This issue was closed because it wasn't updated for 10 days after being marked stale. If it's still important, please reopen + comment and we'll gladly take another look!
Same issue as https://github.com/continuedev/continue/issues/4613.