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
Conversation
Documentation preview for cdb2c3a will be available here when this CircleCI job completes successfully. More info
|
@@ -316,8 +316,15 @@ export class ModelVersionViewImpl extends React.Component { | |||
</a> | |||
); | |||
} else if (runInfo) { | |||
const artifactPath = modelSource.substring(modelSource.indexOf('/artifacts/') + 11); |
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.
@dbczumar Test the case where source run is defined but source
lives outside the run (strange case, but could happen)
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.
@dbczumar Any updates for this comment ? :)
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.
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.
mlflow/server/js/src/model-registry/components/ModelVersionView.js
Outdated
Show resolved
Hide resolved
mlflow/server/js/src/model-registry/components/ModelVersionView.js
Outdated
Show resolved
Hide resolved
Signed-off-by: Weichen Xu <weichen.xu@databricks.com>
mlflow/server/js/src/model-registry/components/ModelVersionView.js
Outdated
Show resolved
Hide resolved
mlflow/server/js/src/model-registry/components/ModelVersionView.js
Outdated
Show resolved
Hide resolved
if (!modelSource) { | ||
throw new Error('model source is missing.'); | ||
} | ||
const artifactPath = modelSource.match(/.+\/artifacts\/(.+)$/)[1]; |
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.
This line seems to assume that modelSource
always ends with /artifacts/...
. What if it doesn't?
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.
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}
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 with two nits left
mlflow/server/js/src/model-registry/components/ModelVersionView.js
Outdated
Show resolved
Hide resolved
/** | ||
* Extract artifact path from provided `modelSource` string | ||
*/ | ||
export function extractArtifactPathFromModelSource(modelSource: string, runId: string) { |
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.
Can we add a return type?
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.
@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 🤔
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.
@hubertzub-db Makes sense!
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 once the remaining comments are addressed
Related Issues/PRs
#8150What 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?
manually test code:
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
(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 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