Does this issue occur when all extensions are disabled?: No (we need the codespaces extension enabled to repro)
- VS Code Version:
- OS Version:
Steps to Reproduce:
Some users have been receiving errors where VSCode does not detect the running process and the ports tab does not populate specifically for IPv6 processes. We believe it's due to VSCode not being able to pick up IPv6 processes as shown below. This issue here causes intermittent issues with port forwarding on the web and this issue does not let the user forward a port.
Here are the repro steps for the second issue:
- Create a Codespace using this repo
- Run
npm init gatsby, cd my-gatsby-site/, npm run develop
- The process is not detected and the ports tab is not updated. Even if you try to add port 8000 to the ports tab, the forwarded port's content is not displayed
- Stop the process from the terminal
- Update
package.json under scripts:develop to be gatsby develop -H 127.0.0.1 and do npm run develop
- The process is detected and the ports tab is updated. If you click on the ports tab you get the forwarded port content
Does this issue occur when all extensions are disabled?: No (we need the codespaces extension enabled to repro)
Steps to Reproduce:
Some users have been receiving errors where VSCode does not detect the running process and the ports tab does not populate specifically for IPv6 processes. We believe it's due to VSCode not being able to pick up IPv6 processes as shown below. This issue here causes intermittent issues with port forwarding on the web and this issue does not let the user forward a port.
Here are the repro steps for the second issue:
npm init gatsby,cd my-gatsby-site/,npm run developpackage.jsonunderscripts:developto begatsby develop -H 127.0.0.1and donpm run develop