IntersectMBO / IntersectMBO/ouroboros-consensus
Cleanup exception handling
Open
:wastebasket: :question: possibly stale
technical debt
- Dominant language
- Haskell
- Stars
- 67
- Forks
- 43
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 43
Description
- [X] The immutable DB should catch `FsError`s and rewrap them accordingly
- [ ] `tryImmDB`, `tryVolDB`, and `tryDB` should probably just go
- [X] It would be nice if the volatile DB would introduce a user error / unexpected error split, just like the immutable DB does; this would clean up the wrapping code in the `ChainDB`.
- [ ] Some of the errors thrown by the volatile DB should perhaps be caught by the volatile DB itself and treated as part of the recovery process.
Contributor guide
Assessment
This issue has not been assessed yet.