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

Fully close unspecified family TCP connections on Windows. #2325

Merged
merged 1 commit into from
Nov 16, 2017

Conversation

chalcolith
Copy link
Member

On Windows, the TCPConnection actor waits for leftover IOCP messages (e.g. from a second happy eyeballs connection when IPv4 or IPv6 is unspecified) before closing, but does not check if it should shut down after such messages are received. This change makes it check again.

This fixes #2322.

On Windows, the TCPConnection actor waits for leftover IOCP messages (e.g. from a second happy eyeballs connection) before closing, but does not check if it should shut down after such messages are received.  This change makes it check again.

This fixes ponylang#2322.
@jemc jemc added changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge and removed needs discussion during sync labels Nov 16, 2017
@jemc jemc merged commit 95a06bb into ponylang:master Nov 16, 2017
ponylang-main added a commit that referenced this pull request Nov 16, 2017
@chalcolith chalcolith deleted the fix_2322 branch November 18, 2017 22:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TCPConnection close/dispose not working on Windows
2 participants