New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminal doesn't always render initially when using PseudoTerminal and task custom execution #94402
Comments
(Experimental duplicate detection) |
@alexr00 here's what the vscode/src/vs/workbench/api/browser/mainThreadTerminalService.ts Lines 116 to 122 in a15ef2c
What task reveal does: vscode/src/vs/workbench/contrib/tasks/browser/terminalTaskSystem.ts Lines 302 to 325 in a15ef2c
|
@GabeDeBacker I'm not able to repro this now. There were some changes in showing tasks in 1.44, do you still see the issue there? |
Fixed a similar issue recently #94714 The problem there was that when an extension created a terminal and did not call show and then another terminal is shown, there were actually 2 terminal tabs visible at once, one not being drawn (the initial one) and one being draw but it was offscreen. |
That was probably it then. I tested in master this time so I had the fix for #94714 |
@GabeDeBacker can you check in Insiders and see if you still have the same problem? |
@alexr00 - Hey, sorry about not responding sooner. Checking now |
@alexr00 - I can confirm that this is indeed addressed in the insiders version. I'm closing this issue. |
VSCode Version: Version: 1.43.2 (system setup)
Commit: 0ba0ca5
Date: 2020-03-24T07:38:38.248Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS Version:
OS: Windows_NT x64 10.0.19600
Steps to Reproduce:
Our extension registers a custom task provider and it provides tasks with custom execution and the following presentation options:
If the terminal "tab" is not already selected for some other reason (say power shell started, etc.) then when the task runs, the terminal dropdown displays the correct task name, but nothing renders.
Note that adding this simple code:
Works around this issue.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: