`splinter_print_lookup` has unsafe race
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 732
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
It's a debug function, but it doesn't handle memtable lookups safely. Should also rename it to indicate the debug functionality.
Contributor guide
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
Locate the splinter_print_lookup implementation and trace how it performs memtable lookups, including any synchronization used by nearby code. The issue is complete when the debug lookup is safe under concurrent access and the function is renamed to clearly indicate its debug purpose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100