Find answers from the community

Updated 9 months ago

bit of a hail mary here, just throwing

bit of a hail mary here, just throwing this out there incase any devs know what might be going on:

in short: the validate_model function for the custom llama index BaseModel (in the deepest darkest depths of the codebase) is since recently somehow destroying perfectly good pydantic output responses (FYI: from a RetrieverQueryEngine with a fairly complex output_cls) at the eleventh hour. I can see that the output is there from the LLM before it hits the validation function, it even gets registered correctly in the event callback and i see the correct outputs in Arize phoenix. But the response from the query engine is just a blank BaseModel.

I can't say rn in exactly what version this cropped up, but certainly somewhere between 0.9 and 0.10. it's a bit of a labyrinth in there, imma write up a proper bug report and create a MWE when I have the time, but taking a shot at fixing it in the meantime as working to a tight deadline.
L
S
6 comments
Yea I think we know the issue, should be a fix out today for it
Basically your PR pointed out the source of the issue -- the end event is converting the response object to something else
Nice one, thank you so much! I put some more details in the linked issue πŸ™‚
automatic type conversion with pydantic is a sneaky one
yeah it's super gnarly, I was half losing my mind in the pydantic source code lol.
Add a reply
Sign up and join the conversation on Discord