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
joaomoreno opened this issue
Feb 23, 2016
· 1 comment
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesimportantIssue identified as high-prioritypolishCleanup and polish issueverifiedVerification succeeded
While successfully debugging using restart: true and nodemon, I created a syntax error and waited. The debugger eventually stopped attempting to connect after 10 seconds. There was no UI error indicating what happened. The console did have errors though.
Note that the error does appear on an initial failed attach attempt:
The text was updated successfully, but these errors were encountered:
@isidorn I've debugged this and it seems that errors returned from 'attach' are only shown in the UI if it is the first 'attach' and not a restarted 'attach'. I tried to find a 'filter' in your code that prevents these error from being shown, but I wasn't successful. Do you have an idea why these errors are not showing up?
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 issuesimportantIssue identified as high-prioritypolishCleanup and polish issueverifiedVerification succeeded
Testing #3238
While successfully debugging using
restart: true
and nodemon, I created a syntax error and waited. The debugger eventually stopped attempting to connect after 10 seconds. There was no UI error indicating what happened. The console did have errors though.Note that the error does appear on an initial failed attach attempt:
The text was updated successfully, but these errors were encountered: