Open
Conversation
Collaborator
Author
|
Maybe not to be merged as is, maybe some subprocesses, such as ifcopenshell.validate, return a non-zero statuscode if there are validation errors (probably 1) then. But any unknown exceptions should be handled. Maybe we should whitelist either 0 or 1, or make this expected statuscodes dependent on the program. But unhandled things somehow have to bubble up to us. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We don't check that the subprocess actually succeeds (returns 0 exit code)
Propagating the typed exception (I think that was my hack) doesn't work because of the CalledProcessError constructor.