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

Do not ignore errors from $spawnExtHostProcess #112033

Merged

Conversation

solomatov
Copy link
Contributor

The callback from the request accepts error as well as undefined. However, we ignore error, when we call then. This change fixes it.

@weinand weinand removed their assignment Dec 7, 2020
@solomatov
Copy link
Contributor Author

There's a similar issue with the $startExtensionTerminal below in the code.

@solomatov solomatov closed this Jan 6, 2021
@solomatov solomatov deleted the error-handling-in-terminal-start branch January 6, 2021 21:10
@solomatov solomatov restored the error-handling-in-terminal-start branch January 6, 2021 21:18
@solomatov solomatov reopened this Jan 6, 2021
Copy link
Member

@Tyriar Tyriar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you elaborate a little how to reproduce the issue this causes?

@Tyriar Tyriar added this to the January 2021 milestone Jan 6, 2021
@solomatov
Copy link
Contributor Author

@Tyriar It made errors where it was impossible to open shell due to errors/exceptions, much more visible. Instead of showing 'Starting...', it shows error message, which gives more troubleshooting info.

For example, it made it easy to diagnose errors like this: #76542 (comment) (It can't get access to parent process env for some reason).

Copy link
Member

@Tyriar Tyriar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's awesome thanks! This should be really helpful on our side too 🙂

@Tyriar Tyriar merged commit b1877cd into microsoft:master Jan 7, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Feb 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants