continue icon indicating copy to clipboard operation
continue copied to clipboard

Dev containers compatibility

Open Cianidos opened this issue 1 year ago • 9 comments

Before submitting your bug report

Relevant environment info

- OS: macOS 14.3.1
- Continue: v0.9.79 (pre-release)
- IDE: VSCode

ollama 0.1.27
using devcontainer

Description

While using tab autocomplete inside dev container, got next message:

Unable to read file '/workspaces/path-to-in-dev-container/main.go' (Error: Unable to resolve nonexistent file '/workspaces/path-to-in-dev-container/main.go')

I think it tries get context, but looks on host, instead real path to volume When I use chat with file as context, everything ok

thanks in advance

To reproduce

open folder in dev container enable tab complete typing

Log output

[Extension Host] Error generating autocompletion:  Error: Unable to read file '/workspaces/go-templ-ctl/src/cli/main.go' (Error: Unable to resolve nonexistent file '/workspaces/go-templ-ctl/src/cli/main.go')
    at n.F (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:657:19968)
    at n.D (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:657:19763)
    at async f.M (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2203:42897)
    at async f.readStream (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2203:42654)
    at async L.Cb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2192:13459)
    at async L.resolve (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2192:11906)
    at async s.W (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2203:39048)
    at async h.r (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2192:25544)
    at async C.acquire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:37:3392)
    at async u.createModelReference (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2192:27121)
p @ console.ts:137

Cianidos avatar Mar 04 '24 22:03 Cianidos

I've seen this, too. I disabled tab-completion to avoid it, though I was hoping to try using it. Containers and remote containers is my normal operating mode.

LTangaF avatar Mar 11 '24 13:03 LTangaF

I also that the option for remote-container/linux will be available as I am developing from windows on a remote linux, and the ollama runs on windows

aharonamir avatar Mar 13 '24 10:03 aharonamir

Local containers just seems like a directory mapping issue. Remote containers may just be that, but it may also be that the extension is largely running in the local chromium environment, but the file browser (etc) is being served up by a remote vscode server

LTangaF avatar Mar 13 '24 14:03 LTangaF

My issue is that the extension runs on the local machine, which is windows but the code is on the remote machine, which is linux. So it cannot access the file on the remote or cannot handle the linux file path (the '/' instead of ')

aharonamir avatar Mar 13 '24 18:03 aharonamir

Also having this issue. Seeing this error:

Unable to read file '\jpaveg\code\tutorials\nextjs\app\lib\data.ts'
(Error: Unable to resolve nonexistent file '\jpaveg\code\tutorials\nextjs\app\lib\data.ts')

The correct filePath should be prepended with home/. Seems similar to a previous issue involving remote containers.

jpaveg avatar Mar 17 '24 09:03 jpaveg

I'm using WSL2 Ubuntu (with Docker too) on my Windows machine, also dockerized containers. I'm getting the same error Unable to read file >> from my wsl2 ubuntu. Any fixes?

kicedz avatar May 03 '24 21:05 kicedz

I'm using WSL2 Ubuntu (with Docker too) on my Windows machine, also dockerized containers. I'm getting the same error Unable to read file >> from my wsl2 ubuntu. Any fixes?

make sure you're on pre-release

jpaveg avatar May 04 '24 04:05 jpaveg

Is this solved?

platform-kit avatar Jun 21 '24 08:06 platform-kit