cockroachdb / cockroachdb/errors
Make the UnimplementedError consider its messages as reportable
Open
- Dominant language
- Go
- Stars
- 2.5k
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
Currently the UnimplementedError constructors consider the messages as always unsafe.
These should be given the same treatement as Newf/Wrapf.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the UnimplementedError constructors and compare their message handling with Newf and Wrapf. Then inspect nearby tests or add coverage for the expected reportability behavior; done means the constructors treat messages consistently and the relevant Go tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100