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

Fix: "Source Run" field in Model Version UI page points to wrong run model artifact in Run UI page #8156

Merged
merged 10 commits into from Apr 12, 2023

Conversation

WeichenXu123
Copy link
Collaborator

@WeichenXu123 WeichenXu123 commented Apr 3, 2023

Related Issues/PRs

#8150

What changes are proposed in this pull request?

Fix: "Source Run" field in Model Version UI page points to wrong run model artifact in Run UI page

Closes #8150

How is this patch tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests (describe details, including test results, below)

manually test code:

import mlflow

import mlflow.sklearn
from sklearn.datasets import load_iris
from sklearn import tree

iris = load_iris()
sk_model = tree.DecisionTreeClassifier()
sk_model = sk_model.fit(iris.data, iris.target)

with mlflow.start_run() as run:
    run_id = run.info.run_id
    print(run_id)
    mlflow.sklearn.log_model(sk_model, "model1")
    mlflow.sklearn.log_model(sk_model, "model2")

    mlflow.register_model(f"runs:/{run_id}/model1", "model01")
    mlflow.register_model(f"runs:/{run_id}/model2", "model02")

Does this PR change the documentation?

  • No. You can skip the rest of this section.
  • Yes. Make sure the changed pages / sections render correctly in the documentation preview.

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.

(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)

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

Components

  • area/artifacts: Artifact stores and artifact logging
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages
  • area/examples: Example code
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
  • area/projects: MLproject format, project running backends
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/server-infra: MLflow Tracking server backend
  • area/tracking: Tracking Service, tracking client APIs, autologging

Interface

  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
  • area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
  • area/windows: Windows support

Language

  • language/r: R APIs and clients
  • language/java: Java APIs and clients
  • language/new: Proposals for new client languages

Integrations

  • integrations/azure: Azure and Azure ML integrations
  • integrations/sagemaker: SageMaker integrations
  • integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • 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/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

Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
@mlflow-automation
Copy link
Collaborator

mlflow-automation commented Apr 3, 2023

Documentation preview for cdb2c3a will be available here when this CircleCI job completes successfully.

More info

Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
@@ -316,8 +316,15 @@ export class ModelVersionViewImpl extends React.Component {
</a>
);
} else if (runInfo) {
const artifactPath = modelSource.substring(modelSource.indexOf('/artifacts/') + 11);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dbczumar Test the case where source run is defined but source lives outside the run (strange case, but could happen)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dbczumar Any updates for this comment ? :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In latest code, if model source is empty or parsing model source failed, it will still jump to the run page. So for some edge case the page won't be broken.

Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
@github-actions github-actions bot added the rn/bug-fix Mention under Bug Fixes in Changelogs. label Apr 4, 2023
Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
if (!modelSource) {
throw new Error('model source is missing.');
}
const artifactPath = modelSource.match(/.+\/artifacts\/(.+)$/)[1];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line seems to assume that modelSource always ends with /artifacts/.... What if it doesn't?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the cases it does not ends with /artifacts/... ?

I think the source string is

[file|s3|...]:/path/to/mlruns/{experiment_id}/{run_id}/artifacts/{artifact_path}

or

mlflow-artifacts:/{experiment_id}/{run_id}/artifacts/{artifact_path}

Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
Copy link
Collaborator

@hubertzub-db hubertzub-db left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with two nits left

Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
@WeichenXu123
Copy link
Collaborator Author

CC @dbczumar @harupy Do you have more comments for this PR ? Thank you!

/**
* Extract artifact path from provided `modelSource` string
*/
export function extractArtifactPathFromModelSource(modelSource: string, runId: string) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a return type?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@harupy my two cents here is that the vast chunk of DB and MLflow typescript codebase relies on implicit inferred return types (in this case string | undefined will be automatically inferred) so it's ok I guess 🤔

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hubertzub-db Makes sense!

Copy link
Member

@harupy harupy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once the remaining comments are addressed

Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
@WeichenXu123 WeichenXu123 merged commit 4728afe into mlflow:master Apr 12, 2023
25 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rn/bug-fix Mention under Bug Fixes in Changelogs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] "Source Run" field in Model Version UI page points to wrong run model artifact in Run UI page
5 participants