-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
InvalidRequestError: Unrecognized request argument supplied: functions #12260
Comments
🤖 Hello, Thank you for reaching out and providing a detailed description of your issue. Based on the information you've provided and the context I've found, it seems that the In the LangChain code, there is a class Therefore, to resolve this issue, you would need to modify the LangChain code or use an adapter to make it compatible with AzureOpenAI. Additionally, there is a similar solved issue in the LangChain repository that suggests updating the I hope this information helps. If you have any other questions or need further clarification, please let me know. Best, Sources
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
System Info
Python 3.11.4
LangChain 0.0.321
Platform info (WSL2):
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"
Who can help?
No response
Information
Related Components
Reproduction
This is my code (based on https://python.langchain.com/docs/use_cases/question_answering/conversational_retrieval_agents and modified to use AzureOpenAI and OpenSearch):
When I execute it, it generates the log error below:
I suspect the
OpenAIFunctionsAgent
is not compatible with AzureOpenAI. I'm not sure. Please check and let me know.Expected behavior
It should be getting a response but LangChain throws an error
The text was updated successfully, but these errors were encountered: