NethermindEth / NethermindEth/pluto
Include stack-traces in errors
@emlautarom1 is already working on this.
Since Sep 17, 2026.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 5
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 37
Description
Description
Currently, we only get stack traces when running in development mode or using RUST_BACKTRACE=1 on panics, but since the idiomatic way of handling errors relies on using Result<T, E> we often miss the context on why an error has been propagated, specifically the exact line of code where the error is raised.
Acceptance criteria
Include stack traces in our Result types in both release and development profiles, without instrumenting all our code. The goal is to have traces "for free" with minimal maintenance cost, and in case an error is propagated to main we should have a full stack trace which shows the exact line where the error was raised.
Documentation link(s)
Potential libraries:
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.
Assessment
This issue has not been assessed yet.