-
Notifications
You must be signed in to change notification settings - Fork 75
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
vscode debug changes cli's test/demo/index.test.js behavior #2702
Comments
After a more than 7 minutes, I finally got the rest of the output. The first line I saw at the same time that I saw the debugger exit. Next you see that I typed a control-C, whereupon the rest of the output showed up. It looks like it contains relevant diagnostics. But "address already in use" may merely be symptomatic of running the non-debug version of the test as I was waiting for more output beyond that reported above.
|
Running it fresh, thereby avoiding the "address already in use" problem, I now get the following, with no control-C needed. However, running it under the debugger takes amazing longer than running it normally.
|
Would be fixed by #2704, as it says in its PR comment. I don't know why github has not done its usual thing and shown that connection here. |
Describe the bug
In the #2701 branch https://github.com/endojs/endo/tree/markm-fix2700-ignore-safe-asynchook-extras , which I hope fixes #2700 so that is no longer an issue, when I run the following in packages/cli
$ yarn test test/demo/index.test.js
in a normal shell, I get a normal successful output.
But when I run it in the vscode JavaScript Debug Terminal, the beginning of the output I get is
Note the "Debugger attached.\nWaiting for the debugger to disconnect" above. I have no idea if that is the problem, but it is likely the normal behavior of running subshells under the vscode JavaScript Debug Terminal
Steps to reproduce
Expected behavior
Platform environment
Additional context
Screenshots
The text was updated successfully, but these errors were encountered: