You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hadayovi opened this issue
Sep 12, 2021
· 5 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Duplicate? I don't know, supposedly it was "fixed" but apparently not quite. #121148 (comment)
Does this issue occur when all extensions are disabled? Yes
VS Code Version: Just auto-updated, 1.60.0
OS Version: Windows 10 Pro 21H1
Steps to Reproduce:
Click the Run and Debug tab on the left of VS Code.
Click the blue Run and Debug button inside of the panel.
Notice that a search box pops up at the top, and shows duplicated environment names as suggestions (?). I can't tell which to of the duplicates to click.
The text was updated successfully, but these errors were encountered:
Same problem here on macOS Big Sur, running:
Version: 1.60.0
Commit: e7d7e9a
Date: 2021-09-01T10:54:53.442Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0
roblourens
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Sep 14, 2021
Hey @connor4312 this comes from having js-debug register its debug adapters twice, with and without pwa-. Would it make sense to remove the languages property from the pwa- DAs?
Note that I'm not coding a PWA, just a local Node.js app only for personal computer use. I don't know if it's relevant for me to say that, but I'm doing very little with VS Code at this time.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Duplicate? I don't know, supposedly it was "fixed" but apparently not quite.
#121148 (comment)
Does this issue occur when all extensions are disabled? Yes
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: