-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken compatibility with BaseLangchainStreamingResponse
when using custom input_variables
#30
Comments
Hi! thanks for bug report! I will look into this. |
@marcovirgolin I don't think there's a bug in the code but likely a small error in how you are using
here Your second question about We use it to run some operation after the chain execution is complete. It is useful in situations where you might want to update a database with new input and chain output. |
Thank you, very possible that I am doing something wrong. Thank you also for explaining background. I know I’m passing a dict correctly. I will try more tomorrow. |
If possible, can you share your script? It will be helpful for me to debug this error. |
@ajndkr my bad, I was missing the tried now with most recent version, using Thank you very much <3 |
I am trying the library with an LLMChain instead of ConversationChain.
My chain has custom inputs.
Say, for example, the prompt is
and thus
This leads to the error:
from BaseLangchainStreamingResponse(StreamingResponse).
LIB VERSION
langchain==0.0.157
fastapi_async_langchain==0.4.3
MY TRACEBACK
This initiates at line 43 of BaseLangchainStreamingResponse:
which gives the exception:
Basically, my input variables are being ignored/lost.
What happens next is that we got in the catch block below,
however
self.background
(which I don't know what it means) has no attributekwargs
SUMMARY
I do not know why but since the recent changes passing of input variables seem to be broken when using
LLMChain
(I don't know about ConversationChain). It was working fine before.moreover, it is assumed that
background
haskwargs
but that might not always the case.The text was updated successfully, but these errors were encountered: