weiqingy commented on issue #723: URL: https://github.com/apache/flink-agents/issues/723#issuecomment-4627919168
@joeyutong Thanks for confirming — sounds like we're fully aligned. Capturing the agreed scope so it's on record: 1. Normalize the framework-owned tool-context payloads in chat_model_action.py so they're checkpoint-safe — covering the UUID used as a dict key as well as the value side, plus output_schema (the Pydantic OutputSchema instance). 2. Document the Python memory value contract: which value shapes are checkpoint-compatible, and that it intentionally diverges from the Java-side contract because Python values have to be materialized across the Pemja boundary before they reach state. 3. Add a Python-side validator at set() that rejects non-checkpoint-stable values early with a clear error, instead of letting them fail during restore. Agreed that failing early is the better trade-off at this stage. Since you've left the PR box unchecked, I'm happy to pick this up. My plan is to land the built-in tool-context fix first as a small self-contained change (it's independent of the contract decision), then follow with the validator and the docs. Does that sequencing work for you? -- 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]
