microsoft / microsoft/vscode-remote-release
[Remote-SSH Bug]: Connection errors are interrupting a reboot on macOS
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
The priority level of a connection error is too high and it blocks MacOS from rebooting.
- You opened or have an open vscode remote development window
- You lose connection such as while moving, disconnect VPN or just don't enter the password (yet).
- You want to reboot your device
- Now vscode blocks MacOS from rebooting because of a connection failure:
- "Try Again" does not work. Now I need to cancel my reboot, press disconnect (that may not even connected before) and do another try for reboot.
Only vscode does this and it is especially annoying when using remote development. Both vscode and vscode remote should address this. Vscode is going to far on the basic notification level and vscode remote is abusing that high notification level for something harmless.
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 reproducing the connection-loss flow with Remote-SSH on macOS while a reboot is pending, then trace which connection error notification is preventing shutdown. Done means a lost or pending connection no longer blocks macOS from rebooting while the relevant error remains available to the user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, vscode
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100