microsoft / microsoft/vscode-remote-release
Allow using only single connection for certain servers to support distributed cluster servers
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
I want to use remote development on the server of my webspace provider.
However, it does not allow to open ports and seems to be backed by a cluster with a distributed ceph file system synchronizing home directories.
While I could solve the port problem by switching to unix sockets this is not sufficient because the socket is created by one connection and tried to be used by another connection. However, another connection is usually mapped to a different cluster node on which it does not even see the socket because /tmp/ is not synchronized. However, even when using a synchronzed folder the socket cannot be opened because it does only work on the cluster node it was created on.
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
No files, tests, or entry points are named. Begin by locating the remote-development connection and Unix-socket handling, then verify behavior against a clustered server where connections can land on different nodes; done means the setup can operate using only one connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100