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
bpasero opened this issue
Sep 27, 2016
· 3 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugimportantIssue identified as high-priorityterminalGeneral terminal issues that don't fall under another labelverifiedVerification succeeded
First of all, if you reach the setTimeout, there is no return value after all (just undefined). And then, how do you know that the process id is there after 200ms?
The text was updated successfully, but these errors were encountered:
bpasero
added
bug
Issue identified by VS Code Team member as probable bug
important
Issue identified as high-priority
terminal
General terminal issues that don't fall under another label
labels
Sep 27, 2016
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 bugimportantIssue identified as high-priorityterminalGeneral terminal issues that don't fall under another labelverifiedVerification succeeded
Testing #12595
See https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/api/node/extHostTerminalService.ts#L44
First of all, if you reach the
setTimeout
, there is no return value after all (justundefined
). And then, how do you know that the process id is there after 200ms?The text was updated successfully, but these errors were encountered: