0.2: Improve error handling
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 425
- Forks
- 163
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 3
Description
Debugging and handling errors is sub-optimal. Our errors are pretty good for the general case, and for just printing an error to a log or whatever, but if you're actually trying to fix bugs or handle the errors programatically, then they are not ideal.
A concrete example is that if an error is thrown while a transaction has not been committed/dropped, then we panic and the underlying error is lost. I think there are other places where an error causes another error and we lose underlying info.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by reproducing the transaction error case described in the issue, then trace other paths where one error causes another; the work is done when underlying error information is preserved instead of being lost or replaced by a panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100