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

Fix WaitForConnectionAsync when NamedPipeServerStream is disposed #52825

Merged

Conversation

manandre
Copy link
Contributor

@ghost
Copy link

ghost commented May 16, 2021

Tagging subscribers to this area: @carlossanlop
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #40674

/cc @jaredpar @davidfowl

Author: manandre
Assignees: -
Labels:

area-System.IO

Milestone: -

@manandre manandre force-pushed the dispose-shared-namedpipeserverstream branch from b13a2c5 to 6e6e7bb Compare May 26, 2021 18:46
@manandre manandre force-pushed the dispose-shared-namedpipeserverstream branch from 6e6e7bb to ef60a2f Compare June 1, 2021 22:09
@manandre manandre requested a review from stephentoub June 2, 2021 21:45
@stephentoub stephentoub merged commit c5edf0e into dotnet:main Jul 18, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Disposing NamedPipeServerStream does not cancel WaitForConnectionAsync
3 participants