fix(core): fail fast when tool schemas can't resolve forward refs during serialization - #39570
Merged
Merged
Conversation
Hunter Lovell (hntrl)
requested a review
from Eugene Yurtsev (eyurtsev)
as a code owner
August 10, 2026 22:52
Hunter Lovell (hntrl)
force-pushed
the
hunter/tool-schema-forward-refs
branch
from
August 10, 2026 22:53
943dd70 to
ebdce17
Compare
Merging this PR will not alter performance
Comparing Footnotes
|
Hunter Lovell (hntrl)
force-pushed
the
hunter/tool-schema-forward-refs
branch
from
August 18, 2026 20:51
1dfda6e to
5212f11
Compare
Sydney Runkle (sydney-runkle)
approved these changes
Aug 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #39099
We currently allow forward refs in pydantic v2 schemas upon creation:
When it comes time to introspect the tool schema (notably in
count_tokens_approximatelyandconvert_to_openai_tool), we rely on signature introspection to extract the tool's input schema. If that contains invalid forward references, there's no schema fields to extract which results in an empty dict:Invalid forward reference MRE
Valid forward reference MRE
The fix is to
.model_rebuild()that raises a pydantic exception if forward references cant be resolvedI'm intentionally not rebuilding pydantic v1 schemas in the same way since
update_forward_refs