microsoft / vscode-js-debug

A DAP-compatible JavaScript debugger. Used in VS Code, VS, + more
MIT License
1.67k stars 283 forks source link

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

Open JNSMDT opened 4 months ago

JNSMDT commented 4 months ago

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

connor4312 commented 4 months ago

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

JNSMDT commented 3 months ago

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.