-
-
Notifications
You must be signed in to change notification settings - Fork 16.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: update_output_model() got an unexpected keyword argument 'auto_delete_file' #9889
Comments
👋 Hello @JeremyCraigMartinez, thank you for your interest in YOLOv5 🚀! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution. If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you. If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available. For business inquiries or professional support requests please visit https://ultralytics.com or email [email protected]. RequirementsPython>=3.7.0 with all requirements.txt installed including PyTorch>=1.7. To get started: git clone https://github.com/ultralytics/yolov5 # clone
cd yolov5
pip install -r requirements.txt # install EnvironmentsYOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):
StatusIf this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training, validation, inference, export and benchmarks on MacOS, Windows, and Ubuntu every 24 hours and on every commit. |
@JeremyCraigMartinez hi, thanks for the bug report! @thepycoder can you take a look at this bug? It looks like a ClearML argument no longer exists but is being passes in the YOLOv5 code. This is occurring in two places in the loggers/intit.py: Should we just delete this argument and problem solved?
|
@thepycoder possible fix for #9889 Signed-off-by: Glenn Jocher <[email protected]>
@thepycoder opened PR #9909 with possible fix, can you please review? |
Hey @glenn-jocher, Sorry for the late reply. Getting rid of the It seems to be breaking because of ClearML version being 1.0.3, which is quite old by now (1y 4m) and didn't have the required parameter yet. So a quick fix for @JeremyCraigMartinez is to update your clearml if possible :) This intergation was written much more recently and didn't take older clearml versions into account. That said, I agree we don't want it to break randomly for people, so wdyt:
FYI: support for this parameter was added in v1.2.0 |
@thepycoder got it! We definitely want to add version requirements then in the commented line in requirements.txt, other than that we can check version on import (with a warning, a pip update, both, or just an assert etc). I'll close #9909. |
@thepycoder opened #9933 with updates to requirements.txt and ClearmL tutorial adding minimum requirements for pip install clearml>=1.2.0 |
@JeremyCraigMartinez the main problem is that your clearml package is out of date (version >=1.2.0 is required with YOLOv5). Please your ClearML with and try again, and let us know if this fixes your problem. Thanks!
|
@thepycoder PR is merged providing better awareness for version constraints with YOLOv5. Let's see how this works and then we can escalate to more measures like version checks on imports if this continues to be a problem. Thank you for your contributions to YOLOv5 🚀 and Vision AI ⭐ |
Search before asking
YOLOv5 Component
Training
Bug
Change from 2 months back seems to be failing. Perhaps a newer version of ClearML stripped this argument. Maybe a fix for this would be to add a version requirements for ClearML or remove it altogether?
Environment
Minimal Reproducible Example
Additional
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: