-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Properly handle return code after error #172
Comments
Bump ! |
I dont see anywhere in discussions this issue is popped up. Could add some more details on severity of this issue please. That should help us to prioritize this fix. |
I have just hit this issue by running the following command:
Or just pass a wrong workflow name. |
We are suppressing the actual exception, which is why the Here is the code snippet of Lines 123 to 162 in 6881543
|
This was previously a workaround when Broker was using multiprocessing instead of multithreading. It should no longer be an issue to bubble this up again. |
Broker should properly handle RC after hitting errors.
Deploy WFs are not in any way special in this.
I won't go grepping broker output for
ERROR
- that's purpose of return codesActual Result:
RC = 0
Expected Result:
RC != 0
The text was updated successfully, but these errors were encountered: