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
isidorn opened this issue
Feb 21, 2019
· 2 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Start debugging a node program
Open dev tools -> notice errors coming from the node extensions
TypeError: Cannot read property 'type' of undefined
at module.exports.t.initializeAutoAttach.e.subscriptions.push.o.debug.onDidStartDebugSession.e (/Users/isidor/Development/vscode/.build/builtInExtensions/ms-vscode.node-debug/dist/extension.js:1)
at Emitter.fire (event.js:480)
at ExtHostDebugService.<anonymous> (/Users/isidor/Development/vscode/out/vs/workbench/api/node/extHostDebugService.js:457)
at Generator.next (<anonymous>)
at fulfilled (/Users/isidor/Development/vscode/out/vs/workbench/api/node/extHostDebugService.js:7)
TypeError: Cannot read property 'name' of undefined
at Function.startSession (/Users/isidor/Development/vscode/.build/builtInExtensions/ms-vscode.node-debug/dist/extension.js:1)
at module.exports.t.activate.e.subscriptions.push.o.debug.onDidStartDebugSession.e (/Users/isidor/Development/vscode/.build/builtInExtensions/ms-vscode.node-debug/dist/extension.js:1)
at Emitter.fire (event.js:480)
at ExtHostDebugService.<anonymous> (/Users/isidor/Development/vscode/out/vs/workbench/api/node/extHostDebugService.js:457)
at Generator.next (<anonymous>)
at fulfilled
The text was updated successfully, but these errors were encountered:
@isidorn this seems to be a VS Code issue: onDidNewSession receives an undefined session (which should not happen).
I've protected extensions from this and I've added two console.errors when this happens.
Is there any more info on what causes this? This fix is throwing errors when launching Dart/Flutter sessions and breaks some of the debugging functionality (see #69534). I can't see what we're doing wrong to trigger it.
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
Start debugging a node program
Open dev tools -> notice errors coming from the node extensions
The text was updated successfully, but these errors were encountered: