This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 129
Better error handling #84
Labels
type: bug
Something isn't working
Comments
merged in #474. We shhould add keyboard handler to handle ctrl+z import sys def my_except_hook(exctype, value, traceback): if exctype == KeyboardInterrupt: print "Handler code goes here" else: sys.__excepthook__(exctype, value, traceback) sys.excepthook = my_except_hook by ondrej |
Tilix4
referenced
this issue
in Tilix4/OpenPype
Mar 23, 2023
* Change: Pyblish Wait for pool futures to finish * change futures key name * black
Tilix4
referenced
this issue
in Tilix4/OpenPype
Mar 24, 2023
* Change: Pyblish Wait for pool futures to finish * change futures key name * black
Tilix4
referenced
this issue
in Tilix4/OpenPype
May 5, 2023
* Change: Pyblish Wait for pool futures to finish * change futures key name * black
Tilix4
referenced
this issue
in Tilix4/OpenPype
Jun 1, 2023
* Change: Pyblish Wait for pool futures to finish * change futures key name * black
Tilix4
referenced
this issue
in Tilix4/OpenPype
Oct 17, 2023
* Change: Pyblish Wait for pool futures to finish * change futures key name * black
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
We need to address error handling through pype. There are two issues:
One is complete user “un-friendliness”. Lot of errors ends up just as tracebacks printed to console (in better cases). For example running application on task on ftract that is not synced to avalon should end with error message saying so, not in “NoneType is not subscritable” or what.
Second is global error handling. We can utilize something like sys.excepthook to catch uncatched exceptions. At that point, try to collect logs from mongo and provide user with ability to report crash to us, or save it to archive and email it manually (default one for headless stuff like event-server)
[PYPE-494] created by ondrejThe text was updated successfully, but these errors were encountered: