microsoft / microsoft/vscode-cpptools
C++ Extension fails to start when viewing a file in a remote workspace over SFTP
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Type: General
Input information below
The
Please review existing issues and our documentation at https://github.com/Microsoft/vscode-cpptools/tree/master/Documentation prior to filing an issue.
Describe the bug
- OS and Version: Microsoft Windows 10 Home Version 10.0.17763 Build 17763
- VS Code Version: 1.28.1 (user setup)
- C/C++ Extension Version: 0.19.0
- Other extensions you installed (and if the issue persists after disabling them): Debugger for Java, Gitconfig Syntax, Java Extension Pack, Java Test Runner, Language Support for Java(TM) by Red Hat, Maven for Java, Remote VSCode, Remote Workspace
- A clear and concise description of what the bug is.
While using Remote Workspace over SFTP with the following test.code-workspace (details obfuscated):
{
"folders":[{
"uri": "sftp://user:pass@myremoteserver.tld/home/user/",
"name": "My SFTP Folder"
}]
}
I opened a .cpp file from an existing project. The extension informed me that it failed to start and was intellisense would be disabled.
To Reproduce
- Insteall C/C++ Extension and Remote Workspace version 0.35.1
- Create a .code-workspace file as detailed above, pointing to a fully updated Ubuntu 16.04.5 LTS server with the appropriate ssh privilages (non-administrator).
- Open any
.cppfile from the file tree now displayed by VSCode. - Observe the error message.
Expected behavior
A clear and concise description of what you expected to happen.
The extension should not crash.
Screenshots
If applicable, add screenshots to help explain your problem.
N/A
Additional context
Add any other context about the problem here including log messages from the Output window.
[Error - 3:57:11 PM] Starting client failed
Launching server using command c:\Users\user\.vscode\extensions\ms-vscode.cpptools-0.19.0\bin\Microsoft.VSCode.CPP.Extension.exe failed.
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 failure with the referenced test.code-workspace, Remote Workspace over SFTP, and a .cpp file, then inspect the C/C++ extension startup output for the Microsoft.VSCode.CPP.Extension.exe launch. Done means the extension starts without the reported error and IntelliSense remains available for the remote file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100