You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2021. It is now read-only.
Right now if a routine called by ModelDriver dies it does not report a "user friendly" error message. We can fix this by catching the error, parsing out the actual error message and displaying it to the user along with the suggestion to submit the detailed error log (the stack trace) to this ticket repository.
The text was updated successfully, but these errors were encountered:
So if I understand, we catch the error, print the error message, drop the full stack trace into an error log, and print a note suggesting the content of the log be posted as an issue in github.
Perhaps we keep just one error log kind of like apache? Keep it in the logs directory? append entries with a time stamp so you can easily tell when the error showed up?
All this sounds good to me, and simple to implement.
Right now if a routine called by ModelDriver
die
s it does not report a "user friendly" error message. We can fix this bycatch
ing the error, parsing out the actual error message and displaying it to the user along with the suggestion to submit the detailed error log (the stack trace) to this ticket repository.The text was updated successfully, but these errors were encountered: