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
SteveShe opened this issue
Sep 6, 2016
· 2 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)
OS Version: Windows 10586.545
The script below should execute and terminate naturally, as it does from a command prompt. Under the VSCode debugger, it executes and then sits in the debugger.
varConnection=require('tedious').Connection;varconfig={userName: 'user',password: 'password',server: 'server001.database.windows.net',options: {encrypt: true,database: 'db001'}}varconnection=newConnection(config);connection.on('error',function(err){if(err){console.log(err);}else{console.log("Error called with no err object.");}});// connection.on('debug', function(messagetext) { // if (messagetext) { // console.log('debugtext: ' + messagetext);// }else { // console.log("Debug called with no messagetext object.");// } // }); connection.on('connect',function(err){// If no error, then good to go...executeStatement();return;});varRequest=require('tedious').Request;functionexecuteStatement(){request=newRequest("select 42, 'hello world'",function(err,rowCount){if(err){console.log(err);}else{console.log(rowCount+' rows');}console.log('About to call connection.close().');connection.close();console.log('Called connection.close().');});request.on('row',function(columns){columns.forEach(function(column){console.log(column.value);});});connection.execSql(request);}
The text was updated successfully, but these errors were encountered:
ramya-rao-a
added
debug
Debug viewlet, configurations, breakpoints, adapter issues
*question
Issue represents a question, should be posted to StackOverflow (VS Code)
labels
Sep 6, 2016
This is not specific to the example code in question. A simple node app with a console.log('hello world'); behaves the same way. From a terminal, this would print hello world and terminate. In debug mode, it prints hello world and waits. Any particular reasoning behind this? @weinand@isidorn
weinand
added
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
*duplicate
Issue identified as a duplicate of another issue(s)
and removed
*question
Issue represents a question, should be posted to StackOverflow (VS Code)
labels
Sep 7, 2016
ramya-rao-a
changed the title
Hang on Windows 10 under VSCode debugger when executing the example code.
Node apps do not terminate in debug mode
Sep 7, 2016
weinand
added
bug
Issue identified by VS Code Team member as probable bug
and removed
*duplicate
Issue identified as a duplicate of another issue(s)
labels
Apr 13, 2017
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 issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)
The script below should execute and terminate naturally, as it does from a command prompt. Under the VSCode debugger, it executes and then sits in the debugger.
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: