-
Notifications
You must be signed in to change notification settings - Fork 227
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
Catch stream exceptions for some Debug Adapter stability. #1022
Catch stream exceptions for some Debug Adapter stability. #1022
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! One question
e is IOException) | ||
{ | ||
// We catch this exception for when the DebugAdapter disconnects while still processing a message. | ||
logger.WriteException("Tried to write to the output stream but it was already closed & broken.", e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This probably happens decently often, do we want to make this a verbose message? If you can't include an exception in the verbose message then never mind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
verbose doesn't allow an exception but I did change this to WriteHandledException
!
…#1022) * catch stream exceptions for Debug Adapter * Use WriteHandledException
This helps protect from a crash we were seeing with the "Start without debugging" feature in VS Code.