MINIFICPP-2766 Preventing C++ exceptions from unwinding the stack ove…#2154
MINIFICPP-2766 Preventing C++ exceptions from unwinding the stack ove…#2154cccs-jsjm wants to merge 1 commit intoapache:mainfrom
Conversation
…r the Python interpreter.
|
Thank you for your contribution! At first glance, your changes seem to do what they're supposed to: catch C++ exceptions, and translate them to Python exceptions. 👍 I'm not sure what happens if no Python stack frame catches the Python exceptions. In that case, letting the exception continue to unwind the C++ stack frames, and eventually rollback the flow file would probably be a better error handling, than letting it become an unhandled Python exception, whatever behavior that means. I didn't test this yet. We may need to change that later. I'd also like to wait for the feedback of @lordgamez, since he has worked quite a bit on the python processor API, he has more insight into the gotchas with python bindings. I'm expecting him to be able to get to this sometime next week, after easter. |
…r the Python interpreter.
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.