-
Notifications
You must be signed in to change notification settings - Fork 78
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
feat: Switch the llm to ChatVertexAI #486
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anubhav756
force-pushed
the
ChatVertexAI
branch
6 times, most recently
from
September 17, 2024 11:36
d0cde79
to
91be445
Compare
anubhav756
force-pushed
the
ChatVertexAI
branch
from
September 17, 2024 11:42
91be445
to
c6231ad
Compare
anubhav756
force-pushed
the
ChatVertexAI
branch
from
September 17, 2024 11:53
c6231ad
to
fbe6ad8
Compare
anubhav756
force-pushed
the
upgrade
branch
7 times, most recently
from
November 14, 2024 19:25
0609128
to
0f04932
Compare
anubhav756
force-pushed
the
ChatVertexAI
branch
from
November 14, 2024 20:02
06a6a10
to
516892d
Compare
Yuan325
reviewed
Nov 14, 2024
anubhav756
force-pushed
the
ChatVertexAI
branch
from
November 15, 2024 09:23
516892d
to
b066cb7
Compare
anubhav756
force-pushed
the
ChatVertexAI
branch
from
November 15, 2024 11:12
b066cb7
to
7f53e54
Compare
anubhav756
force-pushed
the
ChatVertexAI
branch
from
November 18, 2024 21:27
a3fe518
to
ca7380a
Compare
Also use a patched version of langchain-google-vertexai module to address an issue with LangGraph with ChatVertexAI.
This is required to use tool calling feature.
…xAI. ChatVertexAI responds with an AIMessage instead of a plain JSON-formatted string. The string content is in the "content" key of the AIMessage object returned. The issue occurred because now ChatVertexAI responds with a plain string (not a JSON formatted string) when directly responding to a user's query. However, while trying to invoke a tool, it does not provide the corresponding values in "tool_calls" key, but instead returns a JSON-formatted string with tool name and arguments. In this case, the "content" field's string needs to be parsed like before.
anubhav756
force-pushed
the
ChatVertexAI
branch
from
November 19, 2024 15:48
ca7380a
to
5e1c26d
Compare
kurtisvg
approved these changes
Nov 28, 2024
/gcbrun |
1 similar comment
/gcbrun |
…rtexAI. Per langchain-ai/langchain#28271, the fix is to pin pydantic to 2.9.0.
anubhav756
force-pushed
the
ChatVertexAI
branch
from
December 3, 2024 12:10
bea955a
to
f62c559
Compare
anubhav756
pushed a commit
that referenced
this pull request
Dec 3, 2024
🤖 I have created a release *beep* *boop* --- ## [0.3.0](v0.2.0...v0.3.0) (2024-12-03) ### Features * Add similarity threshold to amenity search ([#477](#477)) ([c49bef9](c49bef9)) * Add tracing for AlloyDB and CloudSQL Postgres providers ([#494](#494)) ([2fa03bc](2fa03bc)) * Consolidate postgres providers ([#493](#493)) ([a3b2c42](a3b2c42)) * Reuse connector object across different database connections in… ([#487](#487)) ([61c0f52](61c0f52)) * Switch the llm to ChatVertexAI ([#486](#486)) ([479c5e5](479c5e5)) ### Bug Fixes * Add test cases to improve coverage for postgres and over more tools. ([#508](#508)) ([20870ea](20870ea)) * Reuse connector object across different database connections. ([#484](#484)) ([2b05739](2b05739)), closes [#416](#416) * update close client function to async ([#505](#505)) ([b614276](b614276)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.