Migrate to error type framework with included stack traces
Open
bad error message
enhancement
- Dominant language
- Go
- Stars
- 24.4k
- Forks
- 873
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 108
Description
Dolt errors don't provide stack traces, making it difficult to debug problems and customer issues. Dolt errors should have them and we should enforce their use in all code going forward.
This involves:
1) Picking an error framework to use
2) Migrating all dolt errors to use it
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.