-
Notifications
You must be signed in to change notification settings - Fork 116
Fix OpenAILLM and http_client type #404
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments.
@@ -35,6 +36,24 @@ def test_openai_llm_missing_dependency(mock_import: Mock) -> None: | |||
OpenAILLM(model_name="gpt-4o") | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shall we add more tests for cases like missing http clients, wrong types...?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The http client is not required. And if type is wrong, it will fail later, the user need to fix their code, I think this is not something we can handle internally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea not super important but I meant double checking the intended behaviour is correct not only checking if the instance is of type OpenAILLM
and AzureOpenAILLM
in the unit tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, tests updated, but hold on for a rereview, I'm rethinking a bit the solution
9343071
to
e2ab6f6
Compare
Description
Fixes #401
Type of Change
Complexity
Complexity:
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):