-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Improve the error reporting #242
Comments
@duckinator What would you think of logging the backtrace to a temporary file and giving a link to that (unless the user requests verbose errors via a CLI flag or an environment variable) |
@nbraud I'd be okay with that. Do you think we should tie it to (Sorry for the slow response, in the process of getting a new house.) |
Yes, I think it would make sense not to display the backtrace (and only the exception itself) unless some flag is set, and unconditionally save it to a text file.
I know, hon, and it's entirely fine. I've not been particularly responsive myself either in the last couple of months, and I'm not even moving ;3 |
May be closed by #359. |
Continuation of #240. Currently, the error and warning logs can get pushed off the screen by the backtrace.
The text was updated successfully, but these errors were encountered: