-
Notifications
You must be signed in to change notification settings - Fork 265
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
Debugger gets stuck after attaching. Sometimes works #1683
Comments
Please collect a log file using the instructions in the issue template. The log file location will be written to the Debug Console view, it looks like you've just got what's in the Terminal. That's sometimes useful, but not in this case |
Hey thanks. Is it normal if the log file can't be uncompressed? All of the logs that has been generated have this issue.
|
Yea, it can happen if the log is grabbed before the session ends, but it's still readable. |
Okay, I sent you a log to your email. Thanks for looking into it! |
I'm also hitting this since VS Code 1.78.0, with debug sessions taking an extraordinarily long amount of time to start (They started much faster in the previous VS Code version): |
@segevfiner I'm curious what the log looked like in previous versions. I think your case is caused by fixing the IPv4/6 automatic fallback; I'm guessing sourcemaps for sources like |
@connor4312 Which version would you like me to try and with which VS Code version? |
Installing a Nightly version before 2023.3.29** should work |
Describe the bug
I have a pretty basic launch config which I've hardcoded to run a single test with
jest
. On most runs, it would get stuck atDebugger attached.
. I have toReload window
to resolve it.I have also tried running jest through
jest-cli
,yarn
but same result.To Reproduce
Run launch config.
Occasionally it works. For examples, once it ran 3 times successfully then gets stuck on the 4th. But most of the time it gets stuck.
Additional context: we have a monorepo, use yarn workspaces and I use a multi-root workspace.
For what it's worth, same thing happens when I run
jest
separately and attach the vscode debugger.Log File
VS Code Version: 1.77.3
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: