Avoid changing LHASH data (stats and error) in retrieves
Open
Nobody has claimed this yet.
triaged: feature
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
I hope, given the recent thread-safety drama, this is uncontroversial! :-)
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
Start by tracing the LHASH retrieve path and reviewing the linked thread context about thread safety. Determine which statistics and error data retrieval currently changes, then verify that retrieval leaves both unchanged while preserving the existing lookup behavior; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100