feat: add port forwarding to wsl
Recently I started coding more inside WSL than in Windows, but one issue made me reconsider this: the inability to expose WSL services to other networks with ease. The main discussion about WSL not being able to expose services with ease to other networks can be fount in this [WSL Issue](https://github.com/microsoft/WSL/issues/4150). Thus we could say that this VSCode feature requests aim to be more like a workaround to that issue (that clearly is much more complex and not-soon to be resolved). Would it be possible to import the `Port` tab and the automatic and/or manual Port Forwarding that are available with `Remote-SSH` and `Remote-Tunnel`? To my point of view this shouldn't be much complex, since the Port Forwarding feature is already available. If needed I could write couple of use cases where this could be useful.
Posted by sandros94 on Jun 20, 2023, 10:10 AM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
feat: add port forwarding to wsl
Recently I started coding more inside WSL than in Windows, but one issue made me reconsider this: the inability to expose WSL services to other networks with ease. The main discussion about WSL not being able to expose services with ease to other networks can be fount in this [WSL Issue](https://github.com/microsoft/WSL/issues/4150). Thus we could say that this VSCode feature requests aim to be more like a workaround to that issue (that clearly is much more complex and not-soon to be resolved). Would it be possible to import the `Port` tab and the automatic and/or manual Port Forwarding that are available with `Remote-SSH` and `Remote-Tunnel`? To my point of view this shouldn't be much complex, since the Port Forwarding feature is already available. If needed I could write couple of use cases where this could be useful.
Comments (0)
No comments yet. Start the discussion.