Closed Nicoretti closed 2 years ago
@Nicoretti thanks for reporting this. Panics/stack traces like this should not occur in normal operations. We need to fix the root cause of this error. I created https://github.com/exasol/github-keeper/issues/48 to fix bug.
Since this tool is just for us as a team I'm not sure if it's woth investigating further into nicer error messages in case of softweare issues.
I agree, that we need to distinguish between programming errors (need to be solved at the root) and runtime errors.
Runtime errors need proper user-centric error messages. Short, precise, expressive and with the necessary context. Programming errors just need to be fixed.
An end user whose focus is to fix the issues reported by
github-keeper
is overloaded with "irrelevant" information. On the other hand essential context information to find and address the issue at hand is missing.I will illustrate this based on a recent usage error:
Scenario
Check consistency of
sqlalchemy-exasol
repository.github-keeper
panic: unsupported type float64
-> where was this encountered?file
,line
, ...Acceptance criteria
--debug
flag)file name
,line number
,column
where the error have been encountered. Create a error file e.g. containing stack trace etc. and report to the user where it can be found ...details see error.txt
.--verbose
flag which e.g. then gives status information about current and passed checks e.g.: