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 report a secondary NFW exception after already reporting one earlier. #64412

Merged
merged 3 commits into from Oct 5, 2022

Conversation

CyrusNajmabadi
Copy link
Member

No description provided.


// If this is hit the cancellation token passed to the service implementation did not use the correct token,
// and the resulting exception was not a ConnectionLostException.
return ExceptionUtilities.Unreachable();
Copy link
Member

Choose a reason for hiding this comment

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

Is this the cause of the second NFW?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yup yup!

@CyrusNajmabadi
Copy link
Member Author

@jasonmalinowski going to still wait on you for this to make sure i'm ok on this.

@CyrusNajmabadi CyrusNajmabadi merged commit e19f7de into dotnet:main Oct 5, 2022
@CyrusNajmabadi CyrusNajmabadi deleted the remoteCallbackException branch October 5, 2022 20:45
@ghost ghost added this to the Next milestone Oct 5, 2022
@RikkiGibson RikkiGibson modified the milestones: Next, 17.5 P1 Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants