[BUG] UI Crash - Unterminated string in JSON at position 5000 for mlflow.log-model.history #12032
Open
3 of 23 tasks
Labels
area/tracking
Tracking service, tracking client APIs, autologging
area/uiux
Front-end, user experience, plotting, JavaScript, JavaScript dev server
bug
Something isn't working
Issues Policy acknowledgement
Where did you encounter this bug?
Local machine
Willingness to contribute
Yes. I would be willing to contribute a fix for this bug with guidance from the MLflow community.
MLflow version
System information
Describe the problem
After running trainings using the new version of MLflow we are encountering crashes in MLflow UI.
The issue we encountered results in displaying "Something went wrong", on the experiment screen e.g.
https://mlflow.server/#/experiments/7
. In developer tools console we can observe, that MLflow encountered:We were able to workaround this issue by deleting
mlflow.log-model.history
tag from the db.When the tags are deleted the issue disappears, but appears again after another training.
As far as we can tell, in our case models are usually logged several times whenever a metric is improved. And every time a model is logged, so is its history under the
mlflow.log-model.history
tag. When a model is logged multiple times in a single run, MLflow logs its current history concatenated with its previous history by loading themlflow.log-model.history
tag.Example tag:
Tracking information
Code to reproduce issue
Stack trace
Other info / logs
What component(s) does this bug affect?
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/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, autologgingWhat interface(s) does this bug affect?
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 supportWhat language(s) does this bug affect?
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesWhat integration(s) does this bug affect?
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsThe text was updated successfully, but these errors were encountered: