fix(ai): Handle Pydantic model classes in _normalize_data #5143
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.
Description
Previously,
_normalize_data()would attempt to callmodel_dump()on Pydantic model classes (types) when they were passed as arguments, which would fail. This commonly occurs when model classes are used in schema definitions, such as when passing response format schemas to AI SDKs.This change adds an
inspect.isclass()check to detect when a class type is passed instead of an instance. For classes, we now return a string representation"<ClassType: ClassName>"instead of attempting to callmodel_dump().Changes:
inspectimport tosentry_sdk/ai/utils.py_normalize_data()before callingmodel_dump()tests/utils/test_general.pyBehavior:
model_dump()(existing behavior)"<ClassType: ClassName>"(new behavior)Issues