microsoft / microsoft/vscode-remote-release
git clone git@github.com:robotdad/visualstudio-devcontainer-cpp.git
Open
Nobody has claimed this yet.
ssh
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing open issues and found none that apply.
- If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
- I have read and performed the troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting - My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
- I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot
I asked @remote-ssh and it helped, but I still want to report this bug
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I did not try step 2 of the troubleshooting steps
Remote-SSH Log
Remote-SSH Log
[PASTE LOG HERE WITHIN THE BACKTICKS TO FORMAT]
Expected Behavior
- [
Final-Notifiable-Data-Breaches-Report-Jul-Dec-2021.pdf
](url)
Actual Behavior
Final-Notifiable-Data-Breaches-Report-Jul-Dec-2021.pdf
](url)`
Steps To Reproduce
Anything else?
No response
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 reviewing the Remote-SSH troubleshooting wiki and the issue template. The reported log is only a placeholder, step 2 was not attempted, and the expected and actual behavior contain an unrelated PDF upload, so there is no reproducible entry point or completion criterion yet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 5/100