Repository navigation
examples: verify LangChain ChatOpenAI integration - #798
Merged
Merged
Conversation
acedatacloud-dev
changed the title
acedatacloud-dev
changed the title
Update the example against current main, test adapters 1.6.6 and 1.7.0, and provide runnable setup with canonical acquisition links.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Developers can use LangChain's existing
ChatOpenAIadapter with Ace Data Cloud's Chat Completions endpoint. This change adds a runnable example for synchronous chat, streaming, and a complete two-request tool round trip, plus a reproducible Python environment, application API key setup, and canonical acquisition links that identify the LangChain entry point.The example explicitly selects Chat Completions, disables automatic retries, and distinguishes response token usage from charged Credits. It uses
langchain-openai==1.7.0; CI automatically discovers example tests and covers both 1.6.6 and 1.7.0. The branch incorporates current main (1a09bc80bd1e899db9d9fd159770e54f84bd7648).Validation
git diff --checkpassed. These checks do not send billable API requests.gpt-4o-mini: sync and stream each reported 23 tokens and matching 200 usage records deducting 0.000014191695 Credits. The exact tools example returned5; its two requests reported 82 and 61 tokens and matching 200 records deducting 0.0000420074172 and 0.0000215713764 Credits. Four-request total: 0.0000919621836 Credits. Invalid-token validation returned 401invalid_token; 403/404/429/500 were tested with mocks. No new paid live validation was performed in this follow-up.Publication
Merge this PR before the customer guide, so the guide's example link resolves on main. This change does not publish an Ace-specific provider package. LangChain recommends custom base URLs for standard-compatible endpoints; its official listing process requires a separately published integration package. No official Ace listing is claimed, and acquisition links do not prove signup or first-call conversion.
2026-10-19 shared-main refresh
Incorporates current SDK main
ad57d1d37646d009b7df6e4bb3a5022b4908cf1ewhile preserving its Make App Schema job and this PR's LangChain matrix/lint. No example behavior changed. Exact head7e49e7c85e809fbc258b4eef6c93a3ba60cdb500; new normal CI passed all 11 jobs for this exact head, including the Make schema job: https://github.com/AceDataCloud/SDK/actions/runs/39174991912 . Shared merge is coordinator-owned, before Backend #2116. This remains the standard compatibility example; native ChatAceDataCloud and separate service packages are maintained in https://github.com/AceDataCloud/LangChain .