-
Notifications
You must be signed in to change notification settings - Fork 16
[BUG] Fix aiohttp dep issue #23
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
Conversation
|
does it prevent the package from loading? or is it only necessary when using the DS deployment? If the later we should make this an optional dependency |
| pydantic = ">=2,<3" | ||
| # aiohttp = ">=3.12.14" | ||
| aiohttp = ">=3.12.14" | ||
|
|
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.
does it prevent the package from loading? or is it only necessary when using the DS deployment? If the later we should make this an optional dependency
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.
Making aiohttp required or optional here will likely have little impact since aiohttp is a dependency of LangChain.
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.
@qiuosier Then we should remove it to avoid having version conflicts
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 release failed because of missing aiohttp. @qiuosier @streamnsight https://github.com/oracle/langchain-oracle/actions/runs/17308563396/job/49137511908
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 think the easiest way to move forward is to keep aiohttp. This is unlikely to cause version conflicts.
add aiohttp back as it is required by ds model deployment