fix: allow base64 string in Embedding model to prevent Pydantic warni… #32
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.
…ngs for Azure embeddings
This PR fixes openai#1039 by updating the Embedding response model used for Azure async embedding calls.
Currently, when using the Azure Embeddings API in async mode, the SDK emits Pydantic warnings at every call because the embedding field is strictly typed as List[float]. However, Azure sometimes returns base64‑encoded strings instead of float arrays, which Pydantic tries to validate, resulting in noisy warnings and minor performance overhead.
This change modifies the model to accept both List[float] and str for the embedding field and disables unnecessary validation, preventing Pydantic from trying to coerce base64 strings into float arrays.
Changes being requested
Additional context & links