[BUG] run_name doesn't work with start_run
See original GitHub issueIssues Policy acknowledgement
- I have read and agree to submit bug reports in accordance with the issues policy
Willingness to contribute
Yes. I can contribute a fix for this bug independently.
MLflow version
- Client: 1.30.0
System information
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS Ventura 13.0
- Python version: 3.9.10
- yarn version, if running the dev UI: N/A
Describe the problem
When using MLFlow with the context manager, the specified run_name
isn’t saved to the MLFlow UI.
This issue only happens with version 1.30.0, I tried the following versions as well: 1.27.0, 1.28.0 and 1.29.0. For all of those versions, the run_name
was saved properly.
Tracking information
MLflow version: 1.30.0 Tracking URI: https://XXX.com/ Artifact URI: s3://XXX/XXX/artifacts
Code to reproduce issue
import mlflow
mlflow.set_experiment("mlflow_issue_experiment")
with mlflow.start_run(run_name="test_version_1.30.0"):
mlflow.log_metric("score", 1)
Stack trace
N/A
Other info / logs
No response
What component(s) does this bug affect?
-
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/pipelines
: Pipelines, Pipeline APIs, Pipeline configs, Pipeline 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
What interface(s) does this bug affect?
-
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
What language(s) does this bug affect?
-
language/r
: R APIs and clients -
language/java
: Java APIs and clients -
language/new
: Proposals for new client languages
What integration(s) does this bug affect?
-
integrations/azure
: Azure and Azure ML integrations -
integrations/sagemaker
: SageMaker integrations -
integrations/databricks
: Databricks integrations
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:9 (7 by maintainers)
Top Results From Across the Web
[BUG] Run name not set when using start_run inside ... - GitHub
Please fill in this bug report template to ensure a time. ... [BUG] Run name not set when using start_run inside a MLproject...
Read more >Is it possible to set/change mlflow run name after run initial ...
It is possible to edit run names from the MLflow UI. First, click into the run whose name you'd like to edit. Then,...
Read more >MLflow 2.0.1 documentation
Search can work with experiment IDs or experiment names, but not both in the same call. Values other than None or [] will...
Read more >Track machine learning training runs | Databricks on AWS
Learn about experiments and tracking machine learning training runs using MLflow.
Read more >CircleCI was unable to run the job runner - Build Environment
I am super confused by this error. Having the same problem since morning, but somehow the status page for CircleCi stays all green....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@harupy thanks! I opened a PR. First time I do any open-source so I might’ve missed something.
@dbczumar it seems to be a quite old version,
1.20.2
Thank you guys for the quick feedback in any case 😃
@Cokral We can make the following change to fix this issue. Looking forward to your PR 😃