vscode: Port Forwarding from Azure ML Remote Machine broken with 1.82
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.82
- OS Version: Windows 10
Steps to Reproduce:
-
We are connecting with the Azure Machine Learning Extension to a compute.
-
Before I was able to start a flask server on port 5000, ctrl+click on the terminal output 127.0.0.1:5000 to get the forward by click.
-
In the browser 127.0.0.1:5000 showed the content served via flask.
-
With 1.82 and the new port forwarding, this workflow is broken, even if I hardcode port 5000 in the setting (azureML - Remote.portsToForward)
About this issue
- Original URL
- State: closed
- Created 10 months ago
- Comments: 45 (26 by maintainers)
Commits related to this issue
- Add trace logging to node remote tunnel Investigating #192582 — committed to microsoft/vscode by alexr00 9 months ago
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.82.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
@shsuman Thanks very much. The update indeed fixed all our workloads involving port forwarding. When can we expect a release version of the extension? @alexr00 Thanks for all your efforts and time spent on debugging the issue.
@bloewes I have merged the fix. It should be in our pre release (Azure Machine Learning - Remote) tomorrow sometime after 2AM PDT. Please let me know if it solves your issue.
To install a pre-release version of an extension in Visual Studio Code, please follow the instructions here
@bloewes You can expect the next stable release (0.36.0) sometime this week or early next week.
@shsuman I’d be happy to test a preview extension with vscode insiders with some of our workloads that need port forwarding.
@shsuman it shouldn’t! I would still suggest testing the change before deploying it, but all the other remote extensions made this change a few years ago in response to a different issue: https://github.com/microsoft/vscode-remote-release/issues/145#issuecomment-490063604
Thanks @shsuman and @bloewes. I’m able to reproduce the issue.