dotnet / dotnet/machinelearning-modelbuilder
Error: Failed to validate user configuration and data
@zewditu ci sta già lavorando.
Dal 4/4/2023.
- Lingua principale
- Dockerfile
- Stelle
- 285
- Fork
- 66
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
**System Information (please complete the following information):**
- Model Builder Version (available in Manage Extensions dialog): 17.14.4.2313404
- Visual Studio Version: Microsoft Visual Studio Enterprise 2022 (64-bit) - Current Version 17.5.3
**Describe the bug**
- On which step of the process did you run into an issue:
Object detection on Azure, Training step
- Clear description of the problem:
Initially, there was no prompt from the model builder. In Azure ML Studio, the job failed with the error message, "Error: Failed to validate user configuration and data. 1. Service failed to retrieve the data. Ensure data correctness and availability.", Eventually, the model builder encountered "A network issue has been detected. ", or "Didn't find a child run."
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'Object Detection(Azure)'
2. Setup Environment
3. Select json file
4. Click "Train"
5. Go to Azure ML Studio, see job failed,
**Expected behavior**
A clear and concise description of what you expected to happen.
The job in Azure ML Studio should have succeeded, and the model builder should then consume the model.
**Screenshots**
If applicable, add screenshots to help explain your problem.

**Additional context**
Add any other context about the problem here.
The older version model builder seemed fine, so I rolled back to 16.13.9.2235601, and the issue disappeared.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.