Skip to content
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 39 commits into from
Dec 3, 2024
Merged

feat: Switch the llm to ChatVertexAI #486

merged 39 commits into from
Dec 3, 2024

Conversation

anubhav756
Copy link
Contributor

No description provided.

@anubhav756 anubhav756 deleted the branch main November 15, 2024 10:22
@anubhav756 anubhav756 closed this Nov 15, 2024
@anubhav756 anubhav756 reopened this Nov 15, 2024
@anubhav756 anubhav756 marked this pull request as ready for review November 15, 2024 11:13
@anubhav756 anubhav756 requested a review from a team as a code owner November 15, 2024 11:13
Yuan325 and others added 11 commits November 18, 2024 19:03
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.
Base automatically changed from upgrade to main November 19, 2024 17:12
@anubhav756
Copy link
Contributor Author

/gcbrun

1 similar comment
@anubhav756
Copy link
Contributor Author

/gcbrun

@anubhav756 anubhav756 merged commit 479c5e5 into main Dec 3, 2024
14 checks passed
@anubhav756 anubhav756 deleted the ChatVertexAI branch December 3, 2024 12:41
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants