-
Notifications
You must be signed in to change notification settings - Fork 181
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
Exception in Conversion Does Not Lead to Dangerzone Failing #309
Comments
deeplow
added a commit
that referenced
this issue
Jan 17, 2023
Exceptions raised during the document conversion process would be silently hidden. This was because ThreadPoolExecuter created various threads and hid any exceptions raised. Fixes #309
deeplow
added a commit
that referenced
this issue
Jan 17, 2023
Exceptions raised during the document conversion process would be silently hidden. This was because ThreadPoolExecuter created various threads and hid any exceptions raised. Fixes #309
deeplow
added a commit
that referenced
this issue
Jan 20, 2023
Exceptions raised during the document conversion process would be silently hidden. This was because ThreadPoolExecuter in logic.py created various contexts and hid any exceptions raised. Fixes #309
deeplow
added a commit
that referenced
this issue
Jan 26, 2023
Exceptions raised during the document conversion process would be silently hidden. This was because ThreadPoolExecuter in logic.py created various contexts and hid any exceptions raised. Fixes #309
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To reproduce this, I raised an exception at the end of the conversion process (in
container.py
). However, the program would run fine and not report the exception at all (exit code 0):This can lead to false positives in our testing environment (which currently relies primarily in checking the exit code -- which will need to be revisited soon).
The text was updated successfully, but these errors were encountered: