uNetworking / uNetworking/uSockets
us_socket_write should return -1 on error, not 0
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 307
- PR merge metrics
- No merged PRs in 30d
Description
This is needed to avoid buffering on write failures due to errors.
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 by locating the us_socket_write entry point and inspect how write errors are handled across the implementation. Confirm which error paths currently return 0 and how buffering reacts to them; done means failed writes return -1 rather than 0 without changing successful writes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100