ultralytics / hub

Ultralytics HUB tutorials and support
https://hub.ultralytics.com
GNU Affero General Public License v3.0
107 stars 11 forks source link

Training hub not working #645

Closed ilanb closed 3 weeks ago

ilanb commented 4 weeks ago

Search before asking

HUB Component

Training

Bug

Tried multiple time to start training but nothing happen and after some minutes page reloaded and start training button appear again

Preparing your cloud instance... Hold tight! This could take up to 10 minutes. Thank you for waiting!

After X time message removed and nothing happen, just start training button appear again

Environment

No response

Minimal Reproducible Example

No response

Additional

No response

github-actions[bot] commented 4 weeks ago

👋 Hello @ilanb, thank you for raising an issue about Ultralytics HUB 🚀! Please visit our HUB Docs to learn more:

If this is a 🐛 Bug Report, please provide screenshots and steps to reproduce your problem to help us get started working on a fix.

If this is a ❓ Question, please provide as much information as possible, including dataset, model, environment details etc. so that we might provide the most helpful response.

We try to respond to all issues as promptly as possible. Thank you for your patience!

ilanb commented 3 weeks ago

I already tried Safari and chrome (last version) on OSX, is always same problem, the training don’t start. I already charged 200$ and 20$. For a paid service is not really good… and no support just GitHub… please give some advice or just check my account ?

Best,

Le 17 avr. 2024 à 04:09, Paula Derrenger @.***> a écrit :

Hello! Sorry to hear you're encountering issues with the Training component on the Ultralytics HUB. It sounds like there could be a hiccup with initializing the cloud instance for your training session. A few quick things to try:

Refresh your browser: Sometimes a simple page refresh can resolve the issue. Clear Browser Cache: Stale cache data may sometimes interfere with web applications. Clearing it might help. Try a different browser: This helps determine if the issue is browser-specific. If the problem persists, there might be a temporary issue on our side or a specific issue with your account or setup. Please provide any relevant details (while avoiding sensitive information) such as the browser used, and a screenshot of any error messages (if any) as an update here. This will help us dig deeper into the issue.

Thank you for your patience, and apologies for the inconvenience! We appreciate your support for the YOLO community and the Ultralytics team. 🌟

For more guidelines and troubleshooting tips, you might find our documentation helpful: https://docs.ultralytics.com/hub.

— Reply to this email directly, view it on GitHub https://github.com/ultralytics/hub/issues/645#issuecomment-2060210372, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGYTPK3CD6NNF3QAVFAW3DY5XKVNAVCNFSM6AAAAABGKGFRNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRQGIYTAMZXGI. You are receiving this because you were mentioned.

sergiuwaxmann commented 3 weeks ago

Hello @ilanb! Thank you for reaching out and bringing this to our attention. The message you're encountering is indeed expected behavior as part of the initialization process for your Cloud Training instance. This process involves spinning up a dedicated instance equipped with GPU resources, which can sometimes take a while depending on the current demand and availability of GPU resources.

Maybe you can try starting the process again and share the model ID with us so that we can analyze the logs of your Cloud Training instance? You can find the model ID in the URL of the model page.

ilanb commented 3 weeks ago

Thanks for quick reply, I can understand for the GPU resources but I tried 2 days at day and night…

Model: https://hub.ultralytics.com/models/QrgKsFLsZDLZ9dsW20wi

I use personal dataset from ROBOFLOW too

Best,

Le 17 avr. 2024 à 12:18, Sergiu Waxmann @.***> a écrit :

Hello @ilanb https://github.com/ilanb! Thank you for reaching out and bringing this to our attention. The message you're encountering is indeed expected behavior as part of the initialization process for your Cloud Training instance. This process involves spinning up a dedicated instance equipped with GPU resources, which can sometimes take a while depending on the current demand and availability of GPU resources.

Maybe you can try starting the process again and share the model ID with us so that we can analyze the logs of your Cloud Training instance? You can find the model ID in the URL of the model page.

— Reply to this email directly, view it on GitHub https://github.com/ultralytics/hub/issues/645#issuecomment-2060920129, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGYTPLRCMJPK6JAX6B5GVLY5ZD7RAVCNFSM6AAAAABGKGFRNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRQHEZDAMJSHE. You are receiving this because you were mentioned.

sergiuwaxmann commented 3 weeks ago

@ilanb Maybe the Roboflow dataset wasn't exported from Roboflow properly (issue on their end). If you try starting the Cloud Training again, I can monitor your instance and see if there are any errors.

ilanb commented 3 weeks ago

Just started again now 😉Envoyé de mon iPhoneLe 17 avr. 2024 à 12:32, Sergiu Waxmann @.***> a écrit : @ilanb Maybe the Roboflow dataset wasn't exported from Roboflow properly (issue on their end). If you try starting the Cloud Training again, I can monitor your instance and see if there are any errors.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

sergiuwaxmann commented 3 weeks ago

@ilanb I just checked the logs on your instance and indeed, we have an issue in our logic when we download the Roboflow dataset. Please accept our apologies for the inconvenience caused. Our team is investigating this issue, and we'll update you as soon as we implement a solution. We appreciate your patience and understanding.

sergiuwaxmann commented 3 weeks ago

Hello @ilanb! We just released a new version that fixes the issue you had. Once again, apologies for the inconvenience caused.