Enable preparing nested OutputSchemas for serialization #1357
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.
Currently, the
prep_outputs_for_serialization
function assumes thatpipeline_outputs
cannot be arbitrarily nested (allows up to one level of nesting). This is why, for more complexBaseModels
returned by the python (e.g.TextGenerationOutput
), the function will not properly convert nested numpy arrays to lists for serialization.My diff makes sure that any
pipeline_output: BaseModel
that contains an arbitrary number and nesting depth of any fields that are either aBaseModel
,list
ofnumpy.ndarray
is supported.As a result, we can now serialize logits of the LLM output, that previously was not properly converted from numpy array to a list.
returns