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
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)verifiedVerification succeeded
Once you hit the breakpoint add t to a watch expression -> it is nicely evaluated
Continue the program -> notice how t does not update to not available. This is due to the fact that evalute request is not sending a response
I would expect the evalute to always give a response no matter the state of the program
The text was updated successfully, but these errors were encountered:
isidorn
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Nov 2, 2016
@isidorn with "hit breakpoint" you mean "stopping on the debugger statement", right?
If I press continue, the program comes to an end (but does not correctly terminate because of this long standing node issue) and the watch expression runs into a timeout after 10 seconds (which is the correct behaviour).
If I modify the program by adding some "waiting code" at the end, the "continue" triggers the watch expression which results in an expected "not available" error.
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)verifiedVerification succeeded
Steps to Reproduce:
t
to a watch expression -> it is nicely evaluatedt
does not update tonot available
. This is due to the fact that evalute request is not sending a responseThe text was updated successfully, but these errors were encountered: