report error to client when read request fails
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the problem you're observing
The client hangs after writing data, then trying to read it in the same program. It works if you close the file in between, but it should at least error out if the data has not been synced yet.
### Describe how to reproduce the problem
Run a client application that writes data to a UnifyCR intercepted path, then try to read that data back without closing the file handle before the read. When you do this the client just hangs. This should report an error if the read lookup fails.
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
Reproduce the issue with a client writing to a UnifyCR intercepted path and reading before closing the file handle. Trace the read request and its lookup failure, then verify that the client reports an error instead of hanging when the data has not been synced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100