Skip to content

Fix future issue in sock_connect() #391

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

Merged
merged 1 commit into from
Feb 9, 2021

Conversation

fantix
Copy link
Member

@fantix fantix commented Feb 9, 2021

Use _SyncSocketWriterFuture for cancellation, so that we could remove the writer directly in the callback.

@fantix fantix marked this pull request as ready for review February 9, 2021 02:07
@fantix fantix requested a review from 1st1 February 9, 2021 02:08
Use _SyncSocketWriterFuture for cancellation, so that we could remove
the writer directly in the callback.

Fixes MagicStack#378
Closes MagicStack#389
@fantix fantix force-pushed the t378-use-writer-future branch from 4842175 to acf8841 Compare February 9, 2021 15:46
@fantix fantix merged commit fe3d028 into MagicStack:master Feb 9, 2021
@fantix fantix deleted the t378-use-writer-future branch February 9, 2021 16:29
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.

event loop loop forever: make lots of sock_connec at the same time
2 participants