Added lifecycle stage to run page #4848
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Marijn Valk <marijncv@hotmail.com>
github-actions
bot
added
area/uiux
12 tasks
Signed-off-by: Marijn Valk <marijncv@hotmail.com>
jinzhang21
approved these changes
Sep 28, 2021
There was a problem hiding this comment.
Checked out your PR, and it looks great on my local machine. Thanks for your swift contribution to MLflow, @marijncv !
zbloss
pushed a commit
to zbloss/mlflow
that referenced
this pull request
Sep 28, 2021
* Added lifecycle stage to run page Signed-off-by: Marijn Valk <marijncv@hotmail.com> * Fix whitespace lint errors Signed-off-by: Marijn Valk <marijncv@hotmail.com> Signed-off-by: Zach Bloss <ZachBloss@RockCentralDetroit.com>
zbloss
pushed a commit
to zbloss/mlflow
that referenced
this pull request
Sep 28, 2021
* Added lifecycle stage to run page Signed-off-by: Marijn Valk <marijncv@hotmail.com> * Fix whitespace lint errors Signed-off-by: Marijn Valk <marijncv@hotmail.com> Signed-off-by: Zach Bloss <ZachBloss@RockCentralDetroit.com>
zbloss
pushed a commit
to zbloss/mlflow
that referenced
this pull request
Sep 28, 2021
* Added lifecycle stage to run page Signed-off-by: Marijn Valk <marijncv@hotmail.com> * Fix whitespace lint errors Signed-off-by: Marijn Valk <marijncv@hotmail.com> Signed-off-by: Zach Bloss <ZachBloss@RockCentralDetroit.com>
zbloss
pushed a commit
to zbloss/mlflow
that referenced
this pull request
Sep 28, 2021
* Added lifecycle stage to run page Signed-off-by: Marijn Valk <marijncv@hotmail.com> * Fix whitespace lint errors Signed-off-by: Marijn Valk <marijncv@hotmail.com> Signed-off-by: Zach Bloss <ZachBloss@RockCentralDetroit.com> Signed-off-by: Zach Bloss <zacharybloss@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Marijn Valk marijncv@hotmail.com
What changes are proposed in this pull request?
Added the lifecycle stage of a run to the run page in the UI. This pr closes #4779
How is this patch tested?
Visit the run page in the UI and see the lifecycle stage on the page
Release Notes
Is this a user-facing change?
Lifecycle stage added to the overview of a run on the run page in the UI.
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/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