Fix JSON serialization of team state by handling datetime objects in message dump #6797
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When saving team state to JSON, users encountered a serialization error due to datetime objects in messages:
The issue occurred because
BaseChatMessage
andBaseAgentEvent
classes both have acreated_at
field of typedatetime
, which is not JSON serializable by default.Solution
Changed the
BaseMessage.dump()
method to use Pydantic's JSON-aware serialization mode:This leverages Pydantic's built-in capability to automatically convert datetime objects to ISO 8601 format strings during serialization.
Benefits
Testing
Verified the fix with comprehensive tests covering:
Example of working code after the fix:
Fixes #6793.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.