Correctly implement write deadlines
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Write deadlines should:
- Apply to in-progress writes.
- Shouldn't corrupt the state of the entire connection.
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 connection write path and its deadline handling, then inspect the existing tests around writes and connection state. Verify that deadlines affect writes already in progress without corrupting the entire connection; add or update coverage for both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100