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
Adding agent support to LangChain flavor #8297
Conversation
8f8bbc6
to
76c1ea5
Compare
Documentation preview for ae3a93b will be available here when this CircleCI job completes successfully. More info
|
76c1ea5
to
29f16fb
Compare
from langchain.llms import OpenAI | ||
|
||
assert "OPENAI_API_KEY" in os.environ, "Please set the OPENAI_API_KEY environment variable." | ||
assert "SERPAPI_API_KEY" in os.environ, "Please set the SERPAPI_API_KEY environment variable." |
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.
cc @vladimirk-db @sueann This example can't be used with Databricks model serving because SERPAPI
isn't supported. Something for us to think about in the future :)
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.
LGTM! Great stuff @sunishsheth2009 ! Is there going to be a followup PR to update the flavor description capabilities in models.rst?
+1 @sunishsheth2009 we should make sure to update docs and API docstrings for this :) |
16272ec
to
c23804d
Compare
f6c5762
to
8658b64
Compare
Used for serialization. Also add test that recurses through our subclasses to check they have them implemented Would fix #3217 Blocking: mlflow/mlflow#8297 --------- Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com> Co-authored-by: Dev 2049 <dev.dev2049@gmail.com>
Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com>
Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com>
8658b64
to
6ecb545
Compare
Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com>
88012c6
to
541c4fe
Compare
Used for serialization. Also add test that recurses through our subclasses to check they have them implemented Would fix langchain-ai#3217 Blocking: mlflow/mlflow#8297 --------- Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com> Co-authored-by: Dev 2049 <dev.dev2049@gmail.com>
Used for serialization. Also add test that recurses through our subclasses to check they have them implemented Would fix langchain-ai#3217 Blocking: mlflow/mlflow#8297 --------- Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com> Co-authored-by: Dev 2049 <dev.dev2049@gmail.com>
Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com>
541c4fe
to
afb9a37
Compare
Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com>
6e965a4
to
ae3a93b
Compare
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.
LGTM!
What changes are proposed in this pull request?
Adding agent support to LangChain flavor
How is this patch tested?
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
Adding agent support to LangChain flavor
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes