uNetworking / uNetworking/uSockets
The us_socket_context_connect function is not working properly.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 307
- PR merge metrics
- No merged PRs in 30d
Description
Environment: Windows + libuv.
Issue 1: The system function connect(fd) invoked internally by us_socket_context_connect() is blocked.
Issue 2: When us_socket_context_connect() attempts to connect to a port with no listening service (non-existent port), the on_open callback is incorrectly triggered—this callback should not be invoked in this failure scenario.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at us_socket_context_connect and trace its Windows + libuv connection path. Reproduce both reported cases: the blocked connect(fd) call and a connection to a port with no listening service. Done means the connection is handled without blocking and on_open is not invoked for the failed connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100