microsoft / microsoft/vscode-remote-release
CL arg "--disable-extensions" should not disable remote extensions in remote setup
Open
Nobody has claimed this yet.
bug
remote
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
From https://github.com/microsoft/vscode/issues/97844:
When running VS Code tests in a remote setup with the --disable-extensions option, we should exclude the indispensable remote extensions lile "Remote - SSH" from being disabled. Otherwise the remote setup fails in unexpected ways.
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
Start by tracing handling of the --disable-extensions command-line option in the remote test setup, using the linked VS Code issue 97844 for context. Done means indispensable remote extensions such as Remote - SSH remain enabled while other extensions are disabled, and the remote setup no longer fails unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100