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
When I came across a bug that made the app crash (#9), I had to clone the repo and debug the app myself to be able to report a useful issue, since no errors were reported, and no logs were available (I think?).
It would be great if (at least) the python Traceback output could be easily retrieved by the end user to report their bug, without needing python developer knowledge.
Perhaps the log (as output to the console when run from the command line) could be dumped in a text file in the same directory as the executable on any exception? This should also be documented in the README or usage instructions.
The text was updated successfully, but these errors were encountered:
When I came across a bug that made the app crash (#9), I had to clone the repo and debug the app myself to be able to report a useful issue, since no errors were reported, and no logs were available (I think?).
It would be great if (at least) the python Traceback output could be easily retrieved by the end user to report their bug, without needing python developer knowledge.
Perhaps the log (as output to the console when run from the command line) could be dumped in a text file in the same directory as the executable on any exception? This should also be documented in the README or usage instructions.
The text was updated successfully, but these errors were encountered: