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.

Sign up for GitHub

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

Jump to bottom

Debugger auto attaches when running 'yo' in terminal #794

Closed
mjbvz opened this issue Oct 8, 2020 · 2 comments
Closed

Debugger auto attaches when running 'yo' in terminal #794

mjbvz opened this issue Oct 8, 2020 · 2 comments
Assignees
@connor4312
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone
October 2020

Comments

@mjbvz
Copy link

mjbvz commented Oct 8, 2020 •
edited
Loading

Issue Type: Bug

Repro

  1. With "debug.javascript.autoAttachFilter": "smart"
  2. In VS Code terminal, run yo code

Bug
The debugger starts:

Screen Shot 2020-10-08 at 12 03 02 AM

Extension version: 2020.10.717
VS Code version: Code - Insiders 1.50.0-insider (93c2f0fbf16c5a4b10e4d5f89737d9c2c25488a3, 2020-10-07T00:58:35.624Z)
OS version: Darwin x64 19.6.0
@connor4312
Copy link
Member

I don't have this behavior, can you confirm where the yo script lives, and also make sure it happens if you attach twice in the same workspace? (The bootloader is uploaded lazily, so you can have an old version in your workspaceStorage until the next time you attach)

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Oct 8, 2020
@mjbvz
Copy link
Author

mjbvz commented Oct 9, 2020

It's from nvm: /Users/matb/.nvm/versions/node/v12.14.0/bin/yo

Not sure what the second part means. Just attach to any process twice? Or run yo and have it auto attach twice?

@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Oct 9, 2020
@connor4312 connor4312 added this to the October 2020 milestone Oct 9, 2020
@connor4312 connor4312 self-assigned this Oct 28, 2020
@aeschli aeschli added the verified Verification succeeded label Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@connor4312 connor4312

Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Milestone
October 2020
Development

No branches or pull requests
3 participants
@connor4312 @aeschli @mjbvz