Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up error logging #1245

Rsl1122 opened this issue Dec 8, 2019 · 2 comments

Clean up error logging #1245

Rsl1122 opened this issue Dec 8, 2019 · 2 comments


Copy link

@Rsl1122 Rsl1122 commented Dec 8, 2019

Is your feature request related to a problem? Please describe.

While useful for fixing bugs, users sometimes judge exceptions based on the amount of lines an exception has.
Many exceptions in Plan contain up to 4 causes leading to large stack traces when a single error occurs. Sometimes this is useful, but sometimes it leads to lots of reports of the exception.

Notable Exceptions like this:

  • When Extension fails to register (NoClassDefFoundError, ClassNotFoundException)
  • When a database error occurs (DBOpException, SQLException, SQL specific exception)
    • Especially: Exceptions after database closes ("Database is closed")
  • When Extension method call fails (InvocationException, Causing Exception, Possible other cause)

I would like to be able to..

  • Print a non-scary error message or just enough so that reporting is useful.
  • Better SQL Exception messages by resolving different error codes.
  • (Development) Better manage different exception flows in the code
@Rsl1122 Rsl1122 added this to Backlog (MED Priority) in Active Development Jan 6, 2020

This comment has been minimized.

Copy link
Collaborator Author

@Rsl1122 Rsl1122 commented Feb 12, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Active Development
Backlog (MED Priority)
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.