Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ports forwarding tab disappeared #228253

Closed
Marcdj-02 opened this issue Sep 11, 2024 · 5 comments · Fixed by #228358
Closed

Ports forwarding tab disappeared #228253

Marcdj-02 opened this issue Sep 11, 2024 · 5 comments · Fixed by #228358
Assignees
@alexr00
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders remote-explorer Remote explorer view
Milestone
September 2024

Comments

@Marcdj-02
Copy link

Marcdj-02 commented Sep 11, 2024 •
edited
Loading

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.94.0-insider
  • OS Version: Darwin arm64 24.1.0

Regarding: https://code.visualstudio.com/docs/editor/port-forwarding

  • In the tabs, previously a tab 'Ports' was present, suddenly it disappeared this week
    image

  • Even using the command pallet I cannot find it
    image

Extensions 
  bradlc.vscode-tailwindcss
  code-marc.numbered-comments
  codeforge.remix-forge
  dbaeumer.vscode-eslint
  eamodio.gitlens
  editorconfig.editorconfig
  eliostruyf.vscode-hide-comments
  esbenp.prettier-vscode
  github.copilot
  github.copilot-chat
  github.vscode-github-actions
  github.vscode-pull-request-github
  haskell.haskell
  justusadam.language-haskell
  mikestead.dotenv
  mrmlnc.vscode-scss
  ms-azuretools.vscode-azurecognitivesearch
  ms-azuretools.vscode-azurefunctions
  ms-azuretools.vscode-azureresourcegroups
  ms-azuretools.vscode-docker
  ms-dotnettools.vscode-dotnet-runtime
  ms-python.debugpy
  ms-python.python
  ms-python.vscode-pylance
  ms-vscode.azure-account
  msazurermtools.azurerm-vscode-tools
  orta.vscode-twoslash-queries
  pkief.material-icon-theme
  prisma.prisma
  redhat.vscode-xml
  shardulm94.trailing-spaces
  uctakeoff.vscode-counter
  usernamehw.errorlens
  wallabyjs.console-ninja
  wix.vscode-import-cost
@alexr00
Copy link
Member

alexr00 commented Sep 11, 2024

Can you share your complete list of extensions?

@alexr00 alexr00 added the info-needed Issue requires more information from poster label Sep 11, 2024
@vs-code-engineering vs-code-engineering bot removed the info-needed Issue requires more information from poster label Sep 11, 2024
@Marcdj-02
Copy link
Author

Marcdj-02 commented Sep 11, 2024 •
edited
Loading

@alexr00 I've add my list of extension. As mentioned before, even with all of them disabled (code-insiders --disable-extensions) it does not appear

@alexr00
Copy link
Member

alexr00 commented Sep 12, 2024

@Marcdj-02 the Ports view shouldn't show when there are no extensions installed. It relies on extensions that know how to forward ports to power it. In your list of extensions, I don't see any of the Microsoft extensions that provide port forwarding. It was a bug the view showed before. This look to be working as-designed. Were you using the Ports view for something?

@Marcdj-02
Copy link
Author

@alexr00 Yes, I was using it expose my 3000 port, and access it on another device via a browser. According to the docs (https://code.visualstudio.com/docs/editor/port-forwarding), no extensions are required for this to work, which it has done for the past few months:

Support for port forwarding is built into Visual Studio Code via Microsoft dev tunnels, no extension required. When running a local web service, you can use the Ports view to make the service accessible to others over the internet.

@alexr00 alexr00 added bug Issue identified by VS Code Team member as probable bug remote-explorer Remote explorer view labels Sep 12, 2024
@alexr00 alexr00 added this to the September 2024 milestone Sep 12, 2024
@alexr00
Copy link
Member

alexr00 commented Sep 12, 2024

Thanks @Marcdj-02. @connor4312, looks like it wasn't safe for me to do the check for 2 here: #222854 (comment). I'll enable the view in that case, but not turn on candidate finding.

alexr00 added a commit that referenced this issue Sep 12, 2024
@alexr00
Separate enablment of ports view and featues
c90a5eb 
Fixes #228253
@alexr00 alexr00 mentioned this issue Sep 12, 2024
Merged
alexr00 added a commit that referenced this issue Sep 16, 2024
@alexr00
Separate enablment of ports view and featues (#228358)
36e764a 
* Separate enablment of ports view and featues
Fixes #228253

* Don't add an managedTunnelFactory if there's a resolver

* Only activate onTunnel on startup when there's no remote

* Don't enable ports view if there's tunnel factory but no resolver

* Fix unused import

* Remove unneeded change
@vs-code-engineering vs-code-engineering bot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Sep 16, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexr00 alexr00

Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders remote-explorer Remote explorer view
Projects
None yet
Milestone
September 2024
Development

Successfully merging a pull request may close this issue.

Separate enablment of ports view and featues microsoft/vscode
2 participants
@alexr00 @Marcdj-02