# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19263/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19263/merge#subdirectory=libs/skinny

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/19263/merge

Related Issues/PRs

What changes are proposed in this pull request?

Adding support for multi-turn deepeval scorers.

How is this PR tested?

• Existing unit/integration tests
• New unit/integration tests
• Manual tests

import mlflow
from mlflow.entities.trace_info import TraceMetadataKey
from mlflow.genai.scorers.deepeval import ConversationCompleteness

mlflow.set_tracking_uri("databricks")
mlflow.set_experiment(experiment_id="3011836326718646")

traces = mlflow.search_traces(return_type="list")
session_id = None
for trace in traces:
    session_id = trace.info.trace_metadata.get(TraceMetadataKey.TRACE_SESSION)
    if session_id:
        break

session = mlflow.search_traces(
    return_type="list",
    filter_string=f"metadata.`{TraceMetadataKey.TRACE_SESSION}` = '{session_id}'",
)

print(f"Testing session {session_id} with {len(session)} traces")

scorer = ConversationCompleteness(model="databricks", threshold=0.5)
feedback = scorer(session=session)

if feedback.error:
    print(f"Error: {feedback.error}")
else:
    print(f"Value: {feedback.value}")
    print(f"Score: {feedback.metadata.get('score')}")
    print(f"Rationale: {feedback.rationale}")

outputs:

Testing session 9a14d892-2315-408c-a30e-81edce461425 with 6 traces
Value: yes
Score: 0.6
Rationale: The score is 0.6 because while the LLM addressed some of the user's requests, such as modifying documentation and removing specific emojis, it failed to simplify explanations as the user intended. Additionally, the LLM did not adequately resolve the user's parsing error, merely stating that it should be fixed without confirming the specific issue or providing steps for verification.

Does this PR require documentation update?

• No. You can skip the rest of this section.
• Yes. I've updated:
  • Examples
  • API references
  • Instructions

Will add a follow-up PR for this.

Release Notes

Is this a user-facing change?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

• area/tracking: Tracking Service, tracking client APIs, autologging
• area/models: MLmodel format, model serialization/deserialization, flavors
• area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
• area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
• area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
• area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
• area/projects: MLproject format, project running backends
• area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• area/build: Build and test infrastructure for MLflow
• area/docs: MLflow documentation pages

How 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" section
• rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
• rn/feature - A new user-facing feature worth mentioning in the release notes
• rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
• rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should 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.

• Yes (this PR will be cherry-picked and included in the next patch release)
• No (this PR will be included in the next minor release)