zzwqqq commented on issue #1322: URL: https://github.com/apache/flink-agents/issues/1322#issuecomment-6460014720
Thanks @wenjin272 . I'd reuse `UncapturableException` and move the internal type to `plan.utils` so plan and runtime can share it. Framework faults would be marked where they occur, and `FunctionTool`/`ToolCallAction` would check wrapped causes and rethrow them, using the same classification as the durable and subgraph code. For Python, I'd add an internal counterpart. I tested Pemja: the Java Throwable survives in `RuntimeError.args`, but rethrowing it back to Java loses the cause. I'd use an internal return envelope to carry the original Throwable or Python exception details, then decode and rethrow in Java. I'd cover nested calls and both dispatch paths in Java/Python tests. Any concerns with this direction? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
