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
fix(agama): serialization of undesired content when a flow crashes #6530
Comments
After many rounds of playing with transpiled code I discovered the situation is presented whenever a (flow) function terminates execution abruptly, be it caused by a Java Even Java Serialization of arbitrary variables is already problematic. It is necessary to avoid serialization of unnecessary variables at all cost. A solution has to address the following:
With the two points above, functions will always return a definite value. To implement the solution (ie. no throws) a transpiler rework is required |
When a flow A calls another B, if B crashes and A catches the crash, an undesired behavior occurs when hitting RRF (at A): all variables of B including the expection that caused the crashed are being serialized
Example for more clarity:
In this case, variable
foo2
plus the exception is serialized when the RRF at A is executed. This makes no sense because flow B is already "gone" by then. Surprisingly, even if the caught exception is nulled (E in the example), it tries to serialize itIt is uncertain why Rhino is doing this
The text was updated successfully, but these errors were encountered: