Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release request: include the socket cancellation FD double-close fix (#740)

Open
#766 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
release

Research direction

Review the merged fix in #740 and commit dc680eb20c526d8babacaf4751a12f51431ea246, then inspect the project's release and PyPI wheel publication process. Done means publishing a patch release on GitHub and PyPI that includes the socket cancellation fix and its TCP and Unix socket regression tests.

Written by the indexing model from the issue text.

Description

Thanks for merging #740.

Could you publish a release, including PyPI wheels, containing the socket cancellation / FD double-close fix in commit dc680eb20c526d8babacaf4751a12f51431ea246?

As of September 22, 2026, the latest release on both GitHub and PyPI is still 0.22.1, which does not contain this fix. A normal package upgrade therefore cannot pick it up yet.

The existing upstream report and patch describe a correctness issue: when socket adoption through create_connection(sock=...) or create_unix_connection(sock=...) is cancelled or raises, the Python socket can retain a descriptor already closed by libuv. If that descriptor is reused, subsequent cleanup can close an unrelated connection. The merged patch detaches the socket on the error path and includes TCP and Unix socket regression tests.

A published release would let downstream applications adopt the fix without maintaining custom builds or switching event-loop implementations.

Would a patch release containing #740 be feasible? If a release is already planned, an approximate timeline would be helpful.

Thank you for maintaining uvloop.

Dominant language
Cython
Stars
11.9k
Forks
615
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MagicStack/uvloop

All issues in MagicStack/uvloop

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.