Skip to content
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

PseudoTerminal.open isn't called in some circumstances #84174

Closed
solomatov opened this issue Nov 8, 2019 · 5 comments · Fixed by #84181
Closed

PseudoTerminal.open isn't called in some circumstances #84174

solomatov opened this issue Nov 8, 2019 · 5 comments · Fixed by #84181
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities terminal Integrated terminal issues verified Verification succeeded
Milestone

Comments

@solomatov
Copy link
Contributor

solomatov commented Nov 8, 2019

I have the following problem in one of the extensions:

  • Extension uses Terminal.create with Pseudoterminal API
  • In some circumstances pseudoterminal.open isn't called, though, when I resize and close it, events come

In extHostTerminalService I found the following code:

		let retries = 5;
		while (retries-- > 0) {
			if (this._terminalProcesses[id]) {
				(this._terminalProcesses[id] as ExtHostPseudoterminal).startSendingEvents(initialDimensions);
				return;
			}
			await timeout(50);
		}

It gives only 250ms for terminal to create and it seems that in my circumstances it's not enough. What's worse not even an error message is displayed. It's completely ignored. Could you do something around it, please?

@Tyriar Tyriar added this to the November 2019 milestone Nov 8, 2019
@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities terminal Integrated terminal issues labels Nov 8, 2019
@connor4312 connor4312 added verified Verification succeeded verification-steps-needed Steps to verify are needed for verification and removed verified Verification succeeded labels Dec 5, 2019
@connor4312
Copy link
Member

@Tyriar could you add steps for this?

@Tyriar
Copy link
Member

Tyriar commented Dec 5, 2019

@connor4312 I don't know how to reproduce the problem, an extra code review of the PR might be good enough?

@solomatov could you verify whether the fix worked?

@Tyriar Tyriar removed the verification-steps-needed Steps to verify are needed for verification label Dec 5, 2019
@connor4312
Copy link
Member

Code lgtm

@connor4312 connor4312 added the verified Verification succeeded label Dec 5, 2019
@solomatov
Copy link
Contributor Author

@Tyriar The PR fixes the repro for the problem I had. I haven't encountered this error in other circumstance.s

@Tyriar
Copy link
Member

Tyriar commented Dec 6, 2019

@solomatov thanks, the best verification is from the OP 😃

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities terminal Integrated terminal issues verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants