Skip to content

Conversation

@nohwnd
Copy link
Member

@nohwnd nohwnd commented May 29, 2023

Description

Avoid forwarding stack error when testhost disconnects unexpectedly. This error steals developer focus from the other more important error, which is either the testhost error message, or simply "testhost crashed" without any additional info.

Related issue

Fix #4461

Kindly link any related issues. E.g. Fixes #xyz.

  • I have ensured that there is a previously discussed and approved issue.

remoteEndPoint,
localEndPoint);
error = ioException;
// Do not pass the error to the caller, the transport was torn down because testhost
Copy link
Member Author

Choose a reason for hiding this comment

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

Not super happy about this, but if we do it later in the code we end up ignoring errors for all types of transports (we have just 1 type now, but the abstractions are there). Or we have to match a specific type of error, and then make sure it was raised here, which is pretty much the same as not raising it at all.

@nohwnd
Copy link
Member Author

nohwnd commented May 29, 2023

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@nohwnd nohwnd enabled auto-merge (squash) May 29, 2023 15:38
@nohwnd nohwnd merged commit 9938cd8 into microsoft:main May 29, 2023
This was referenced Jul 22, 2025
This was referenced Jan 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

don't dump stack of parent when child process exits unexpectedly

2 participants