Open amihalik opened 1 year ago
I see the general problem here - we're checking the OS of the host when deciding whether to format paths with forward or backslashes, and the host is Windows, so sends paths with the wrong separator. I'd assume these paths exist if given the correct separator (in the Debian container).
Mostly a note to myself, but the requirement to solve this is just finding a reliable way of determining the OS of the dev container or remote machine (vscode.workspace.fs
doesn't seem to provide anything out-of-the-box). I'll give this a short tmr
I have a similar problem. I use CodeServer. When I try /edit write a bash script
same happens but with a different error message that leads I guess to the same problem
error handling message (showDiff) from Continue server: Error (FileSystemError): Unable to resolve filesystem provider with relative file path 'vscode-remote://cs.dev.treehouse.corpremoteagent'
cs.dev.treehouse.corp
is the remote host in my local network where the code-server is running
I note $backslash
in the error there:
'vscode-remote://dev-container\tmp\continue\$backslash$workspaces$backslash$python-2$backslash$hello_world.py'
Could it be this is a solved problem and you just need to use $backslash
instead of \
?
@sestinj , the above message was meant for you. It seems there is already something at play that distinguishes which backslash to use (possibly provided by vscode), can you just use $backslash instead of doing the hard work of reliably determining the OS of the dev container or remote OS?
@gemmell very sorry I missed this! The "$backslash" here was replaced with "f" or "b" in more recent versions, the relevant code being here, and we made a number of related fixes in just the last few weeks. Is this still happening for you on latest versions? If so, what's the best way for me to set up an environment like yours to reproduce?
Hello team, are you officially supporting CodeServer? Thanks
Before submitting your bug report
Relevant environment info
Description
It seems like commands like
/comment
don't know where my files are when I'm working in a dev container. For instance, I tried to add comments to a fileconfig.py
in my project, and I got these errors in the Developer Tool:To reproduce
Here's an clean example on a new project:
print('hello world')
)/comment
Log output
No response