grandecola / grandecola/bigqueue
Handle fsync errors better
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 454
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Reference: https://www.usenix.org/conference/atc20/presentation/rebello
Resources: https://github.com/wiscadsl
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
No files, tests, or expected behavior are named. Start by reading the persistence and fsync handling in the bigqueue repository, then review the linked USENIX paper and wiscadsl resources. Define the error cases and desired handling before adding regression coverage and verifying that fsync failures are reported correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100