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
Anki's default exception handler seems to use showInfo and strips information like the stack trace. This makes it hard to debug issues, such as #1.
We should intercept Anki's exception handler to:
Show more useful information (such as the exception type, the location in code [if possible], and the whole message).
Direct the user to submit a ticket on GitHub.
Log the stack trace.
If SmoothBrain moves to a web API, we should probably send the log to us (conditioned on the user opting in to submit information to us to improve the program).
The text was updated successfully, but these errors were encountered:
Intercepting exceptions causes Anki to crash if the exceptions occur in one of Anki's Op threads. So I'd either need to make it single threaded, or make my own multithreading code (which I tried before, which also crashed Anki).
We can tell Anki not to intercept exceptions in CollectionOp by something like this, which will actually trigger another exception handler in Anki that shows debugging instructions and the stack trace:
Anki's default exception handler seems to use
showInfo
and strips information like the stack trace. This makes it hard to debug issues, such as #1.We should intercept Anki's exception handler to:
If SmoothBrain moves to a web API, we should probably send the log to us (conditioned on the user opting in to submit information to us to improve the program).
The text was updated successfully, but these errors were encountered: