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.

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

debug URL timeouts when using debug terminal in wsl. #2037

Open
JNSMDT opened this issue Jul 13, 2024 · 2 comments
Open

debug URL timeouts when using debug terminal in wsl. #2037

JNSMDT opened this issue Jul 13, 2024 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@JNSMDT
Copy link

JNSMDT commented Jul 13, 2024

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:

  1. Open debug terminal
  2. Start vite dev server
  3. 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

@JNSMDT JNSMDT added the bug Issue identified by VS Code Team member as probable bug label Jul 13, 2024
@connor4312
Copy link
Member

If you run the "Toggle Developer Tools" command, are there any logs there?

@JNSMDT
Copy link
Author

JNSMDT commented Aug 2, 2024

Hey,

sorry for responding that late.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants