OpenZeppelin / OpenZeppelin/Event-Scanner
ref: Error Messages Should be More Descriptive, i.e. by Containing Context Where They Occurred
Open
Nobody has claimed this yet.
priority: low
type: enhancement
type: refactor
- Dominant language
- Rust
- Stars
- 19
- Forks
- 7
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 4
Description
The BlockNotFound error is returned from multiple places, the client wouldn't know where exactly the error occurred.
Errors should contain additional context on where exactly they occurred, or during which process.
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
Search the codebase for the BlockNotFound error and identify each place that returns it. Trace the surrounding operations to determine what context distinguishes those locations; the work is done when errors identify where or during which process the failure occurred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100