don't report communication error on discovery abort #14992
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jul 21, 2025
Closed
Closed
Closed
Closed
This was referenced Sep 17, 2025
Closed
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When TE is "cancelling" discovery, it issues the abort command and that will close the communication channel. If the proxy is writing the request into it there will be an exception saying that we could not write to the channel. We already cancelled so we don't need to report this, since this is a race condition and user cannot do anything about the "error".
Related issue
https://devdiv.visualstudio.com/DevDiv/_queries/edit/2016626/?queryId=a6567881-6d43-4514-bab9-161652f32037