lambdaclass / lambdaclass/ethlambda
Handle malformed DB data
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Description
See #443 for an example. In decode_live_chain_key we don't check the key length before decoding, leading to a possible panic. We should gracefully handle this.
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 at the decode_live_chain_key entry point and read the example in issue #443 to understand the malformed key shape. Verify the current behavior with malformed database data, then ensure invalid key lengths are handled without a panic and confirm the existing valid-key behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100