Open jannek opened 4 years ago
I was able to reproduce the error in a wsl-remote session, I got (standard installation in win10):
[10:52:00.454] [ERROR]
[10:52:00.456] [ERROR] Failed to process input. See Exception below.
Error: cannot open vscode-remote://wsl%2Bubuntu/c/Users/[my user]/.vscode/extensions/ms-vscode-remote.remote-wsl-0.39.9/C%3A/Users/[my user]/Synced/Notizen/Journal/2019/10/24.md. Detail: Unable to read file (Error: File not found (vscode-remote://wsl+ubuntu/c/Users/[my user]/.vscode/extensions/ms-vscode-remote.remote-wsl-0.39.9/C:/Users/[my user]/Documents/Synced/Notizen/Journal/2019/10/24.md))
at n.then.e (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:4707:361)
at process._tickCallback (internal/process/next_tick.js:68:7)
Do you expect the journal file to be created in your local environment or on the remote server? The journal path from the settings is configured for your local environment only, it makes sense that the extension cannot find the path on the remote server.
In this case I expect the file to open on the remote server (my workspace is opened there), not sure how to properly configure this for general use case.
Did you notice that the file is created after all on remote, and can be opened without errors next time?
@jannek I am having the same issue. When I first try and open a new file, I get an error but after that if I try a second time it works without a problem. Hopefully this can be fixed because its a pain.
+1 I am also seeing the same issue. Here's what I see:
It's livable, but annoying enough that I thought I would comment on the issue and see if I could help. Thanks!
Same here. It works somehow, but the error code and the additional step to reopen the created file is annoying. Would be nice to get some fix/workaround.
If a remote development method is used (ssh in this case), new journal file creation gives an error, but apparently succeeds as subsequent access to file location works fine.
Repro:
If file does not already exist, following error is logged: