You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I use the debug terminal in windows, starting the vite devserver and xtrl+click the URL a new chrome window appears and I can debug my application.
When I'm in wsl the devserver starts but ctrl+click just opens chrome but never opens the url nor attach the debugger with then leads to a timeout error.
To Reproduce
Steps to reproduce the behavior:
Open debug terminal
Start vite dev server
Ctrl +click url
4a. Works when in windows
4b. Doesn't work when in wsl
Log File
I don't habe a launch file since it always worked for me in windows.
VS Code Version: 1.91.1
Don't know if this is really a bug, but all the issues that mentioned wsl didn't had the right hint or same problem then I do. Maybe it's just a misconfiguration then I already apologize
The text was updated successfully, but these errors were encountered:
JNSMDT
added
the
bug
Issue identified by VS Code Team member as probable bug
label
Jul 13, 2024
When i try to launch chrome via ctrl + click for the first time i get three times an 408 Error (running browser: Unexpected server response: 408). If i ctrl + click after that, i don't get that message again, but still get the timeout error.
Describe the bug
When I use the debug terminal in windows, starting the vite devserver and xtrl+click the URL a new chrome window appears and I can debug my application.
When I'm in wsl the devserver starts but ctrl+click just opens chrome but never opens the url nor attach the debugger with then leads to a timeout error.
To Reproduce
Steps to reproduce the behavior:
4a. Works when in windows
4b. Doesn't work when in wsl
Log File
I don't habe a launch file since it always worked for me in windows.
VS Code Version: 1.91.1
Don't know if this is really a bug, but all the issues that mentioned wsl didn't had the right hint or same problem then I do. Maybe it's just a misconfiguration then I already apologize
The text was updated successfully, but these errors were encountered: