fix: resolve Pydantic serialization warning for context in SubAgent (issue #430) #436
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eyurtsev
approved these changes
Nov 24, 2025
Author
|
This is ready to merge! @eyurtsev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes a PydanticSerializationUnexpectedValue warning observed when running subagents.
Issue: The runtime argument in task and atask functions lacked the generic type annotation [ContextT]. This caused the Pydantic serializer to expect None for the context field, resulting in a warning when a valid Context object was passed.
Changes:
Imported ContextT from langchain.tools.tool_node.
Updated type hints from ToolRuntime to ToolRuntime[ContextT].
Error Log Resolved:
PydanticSerializationUnexpectedValue(Expected none - serialized value may not be as expected [field_name='context', input_value=Context(...)])
Linked Issue
Closes #430