-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Groq autotracing #14006
Groq autotracing #14006
Conversation
Signed-off-by: Anumita Dasgupta <anumita0302@gmail.com>
Signed-off-by: Anumita Dasgupta <anumita0302@gmail.com>
@anumita0203 Thank you for the contribution! Could you fix the following issue(s)? ⚠ DCO checkThe DCO check failed. Please sign off your commit(s) by following the instructions here. See https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.md#sign-your-work for more details. |
Documentation preview for bb3263a will be available when this CircleCI job More info
|
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.
Aside from the documentation, could you update a few more files to make CI pass? Reference: https://github.com/mlflow/mlflow/pull/13851/files
- Add
tests/groq
to theconftest.py
- Add
groq
to the ml-package-versions.yml file. The file defines supported versions and some installation commands for the CI. You can follow the format ofanthropic
. For maximum version, please set the latest version. Minimum version doesn't have to be very accurate.
mlflow/groq/__init__.py
Outdated
from mlflow.groq._groq_autolog import ( | ||
patched_call, | ||
) |
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.
from mlflow.groq._groq_autolog import ( | |
patched_call, | |
) | |
from mlflow.groq._groq_autolog import patched_call |
mlflow/groq/__init__.py
Outdated
if Version(_get_groq_package_version()) < Version("0.13.0"): | ||
raise MlflowException("Groq autologging is only supported for groq >= 0.13.0") |
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.
Once you added the minimum version in ml-package-versions.yml
, you can remove this validation🙂
mlflow/groq/_groq_autolog.py
Outdated
ChatCompletions: SpanType.CHAT_MODEL, | ||
Embeddings: SpanType.EMBEDDING, | ||
} | ||
return span_type_mapping.get(task, SpanType.UNKNOWN) |
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.
return span_type_mapping.get(task, SpanType.UNKNOWN) | |
return span_type_mapping.get(task, SpanType.LLM) |
Let's use LLM type for translation / translations
mlflow/groq/_groq_autolog.py
Outdated
config = AutoLoggingConfig.init(flavor_name=mlflow.groq.FLAVOR_NAME) | ||
active_run = mlflow.active_run() | ||
|
||
# Active run should always take precedence over the run_id stored in the model | ||
run_id = active_run.info.run_id if active_run else getattr(self, "_mlflow_run_id", None) |
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.
Only trace logging is required for now, so we don't need to manage Run logic. You can refer to anthropic implementation to simplify the logic here. (Sorry I should have refer it instead of OpenAI in the guidance).
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.
Great test coverage!
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.
Thanks 😊
Signed-off-by: Anumita Dasgupta <anumita0302@gmail.com>
Signed-off-by: Anumita Dasgupta <anumita0302@gmail.com>
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 change overall looks great! I think we are very close to the goal🙂
A few more formal changes to make things work and test pass:
- Add
groq = LazyLoader("mlflow.groq", globals(), "mlflow.groq")
in mlflow/init.py to allow lazy import. - Add
"groq": "mlflow.groq"
to this dictionary so that it is integrated to the globalmlflow.autolog()
API.
Once these are addressed, we should be good to merge and release this in next month. Thank you for putting effort on this, @anumita0203 !!
tests/groq/test_groq_autolog.py
Outdated
return DUMMY_CHAT_COMPLETION_RESPONSE | ||
|
||
|
||
def test_chat_completion_autolog(): |
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.
According to the error message here, it seems we need to set some dummy API key in the environment variable for testing, even if we patch the client.
mlflow/groq/__init__.py
Outdated
def _get_groq_package_version(): | ||
return importlib.metadata.version("groq") |
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.
nit: we can remove this function
Signed-off-by: Anumita Dasgupta <anumita0302@gmail.com>
Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com>
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!
Signed-off-by: Anumita Dasgupta <anumita0302@gmail.com> Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Signed-off-by: B-Step62 <yuki.watanabe@databricks.com> Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Co-authored-by: B-Step62 <yuki.watanabe@databricks.com> Signed-off-by: k99kurella <karthikkurella4@gmail.com>
Signed-off-by: Anumita Dasgupta <anumita0302@gmail.com> Signed-off-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Signed-off-by: B-Step62 <yuki.watanabe@databricks.com> Co-authored-by: Yuki Watanabe <31463517+B-Step62@users.noreply.github.com> Co-authored-by: B-Step62 <yuki.watanabe@databricks.com> Signed-off-by: k99kurella <karthikkurella4@gmail.com>
🛠 DevTools 🛠
Install mlflow from this PR
Checkout with GitHub CLI
Related Issues/PRs
Resolve #13911
What changes are proposed in this pull request?
Add Autolog tracing integration for Groq.
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
Add Autolog tracing integration for Groq.
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/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/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/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" 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 notesShould this PR be included in the next patch release?
Yes
should be selected for bug fixes, documentation updates, and other small changes.No
should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.