deckhouse / deckhouse/yandex-cloud-controller-manager
Ensure proper and consistent error handling throughout the program
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 107
- Forks
- 13
- Avg merge
- 23h 39m
- Merged PRs (30d)
- 1
Description
Currently, we've got nil values, empty slices, sentinel errors from external packages. All clashing up in an incoherent untestable mess.
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
The issue does not name any files, tests, or entry points. Start by inventorying the program's nil values, empty slices, and sentinel errors from external packages, then define a consistent, testable error-handling approach. Done means the error paths follow that approach throughout the program and are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100