Error INVALID_PARAMETER_VALUE mlflow exceptions with Yolov8
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, python
- Domain
- cloud, machine-learning
Research direction
The report names no repository file, notebook, or test to start from. Begin by reproducing the Azure ML YOLOv8 training run with mlflow.autolog enabled, then inspect the run and exception details; done means the job records its graphs, metrics, and parameters without ending in INVALID_PARAMETER_VALUE or a failed status.
Written by the indexing model from the issue text.
Description
I have problems with training a model in Azure ML, I'm trying train a Yolov8 model for object detection and I just use mlflow.autolog() and the version of mlflow is the last, but I have the error:
mlflow.exceptions.RestException: INVALID_PARAMETER_VALUE: Response: {'Error': {'Code': 'ValidationError', 'Severity': None, 'Message': 'The request is invalid.', 'MessageFormat': None, 'MessageParameters': None, 'ReferenceCode': None, 'DetailsUri': None, 'Target': None, 'Details': [], 'InnerError': None, 'DebugInfo': None, 'AdditionalInfo': None}, 'Correlation': {'operation': '262191915b4055bf8d6ca5b81e232344', 'request': 'dfd448b0dff6cbed'}, 'Environment': 'eastus', 'Location': 'eastus', 'Time': '2023-07-05T19:46:04.6606402+00:00', 'ComponentName': 'mlflow', 'error_code': 'INVALID_PARAMETER_VALUE'}
I was trying to use the parameters too:
run = mlflow.start_run()
mlflow.set_experiment(experiment_name='')
mlflow.end_run()
Different commbination but I have the same error.
The information of the job (graphs, metrics, parameters) are save and show in the canvage of Azure ML but the job in the end show the error and show like a job failed.
- Dominant language
- Jupyter Notebook
- Stars
- 4.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/MachineLearningNotebooks
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Azure/MachineLearningNotebooks#1975 · 1 comment ·
-
duplicates Open
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Azure/MachineLearningNotebooks#1960 ·
-
machine Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
Azure/MachineLearningNotebooks#1987 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/MachineLearningNotebooks#1985 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Azure/MachineLearningNotebooks#1981 · 1 reaction ·
All issues in Azure/MachineLearningNotebooks
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#141 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
documentation improve or update documentation priority/low triage
Difficulty 2/5 Half a day Newbie friendliness 86/100
warpdotdev/docs#782 · 1 comment ·
-
customer-reported question
Difficulty 1/5 Under an hour Newbie friendliness 80/100
Azure/awesome-azd#1017 ·