bregman-arie / bregman-arie/ci-runner
Introduce proper exceptions
Open
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Right now exceptions are LOG.error(...) + sys.exit(2) which is terrible.
Work has to be done to convert such code into proper custom exceptions.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, entry points, or tests are named. Start by locating the LOG.error(...) and sys.exit(2) paths, inventory each affected flow, and identify the existing application boundaries before defining the scope of the custom-exception conversion; done means those paths use proper custom exceptions instead of the described pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100