microsoft / microsoft/vscode-remote-release
Allow to open vscode:// urls in remote
Open
Nobody has claimed this yet.
feature-request
ssh
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.54.3, Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
- Local OS Version: macOS Catalina 10.15.7 (19H524)
- Remote OS Version: Ubuntu 20.04.1 LTS
- Remote Extension/Connection Type: SSH
Steps to Reproduce:
- Open a project in VSCode remote that has a file at absolute path
/my/file/path.js - Click on a link (in Chrome, on Mac machine running vscode) with url "vscode://file/my/file/path.js"
- Get error modal in open VSCode window with title "Path does not exist", body: "The path '/my/file/path.js' does not seem to exist anymore on disk."
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No
This is following the vscode:// schema feature described in https://code.visualstudio.com/docs/editor/command-line#_opening-vs-code-with-urls
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the vscode://file URL flow with the listed VS Code, macOS, Ubuntu, and SSH setup. Start at the remote URL and file-opening entry point and compare it with local behavior; done means the remote file opens without the “Path does not exist” modal while local opening still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100