Handle malformed DB data

Open Beginner friendly
#529 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
blockchain

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.

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.

Dominant language
Rust
Stars
82
Forks
28
Avg merge
1d 23h
Merged PRs (30d)
19

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambdaclass/ethlambda

All issues in lambdaclass/ethlambda

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.