RexOps/Rex

Better error handling

Open

#991 opened on Mar 11, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Perl (218 forks)batch import
help wantedtask

Repository metrics

Stars
 (671 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Currently we don't have a proper error handling. We throw exceptions at multiple places, some get caught others not. Also the exceptions are just strings so a proper handling of these exception can't be guaranteed.

To solve this, we need to define a proper way to throw and catch exceptions. We also need to have more detailed error messages for 2 kind of users. One for novice users who don't know the internals and one for powerusers/developers with stacktraces and other interessting stuff.

Some linked issues: #959 #949 #671 #477 #489 #343

Contributor guide

Research direction
Examine existing exception handling in the codebase, identify patterns, and propose a structured error handling approach with user level error messages and developer stack traces.
Tech stack
perl
Domain
devopsbackend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPerl
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75