Discussion: download and upload models have a somewhat inconsistent API
See original GitHub issueHi all. Just a small-ish thing to discuss.
Methods that get information about/from repos take the full model id (e.g. hf_api.model_info("osanseviero/my-model")
or snapshot_download("osanseviero/my-model)
).
On the other hand, create_repo
takes as two separate arguments the model name and the organization (if any). I wonder if this could lead to confusions in the future, and, if so, we should check if the name param has a /
and determine if there’s an org in there.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Inconsistent attachment download - SMA-Service Manager Suite
My customer having problem downloading the attachement. Usually pdf files ( 200 - 400kb max). ... The problem is the opening file time...
Read more >Inconsistent errors with check --read-data - Getting Help
After a while, I think the issue should be fixed, but the restic check --read-data returns errors. I thought this was weird because...
Read more >An overview of the CellML API and its implementation
CellML is an XML based language for representing mathematical models, in a machine-independent form which is suitable for their exchange ...
Read more >Turning Machine Learning Models into APIs with Python Flask
Learn to how to make an API interface for your machine learning model in Python using Flask. Follow our step-by-step tutorial with code...
Read more >Document changes to file upload permissions in Django 1.11
I have models: MainModel() and ... Been hitting the same issue although it's somewhat inconsistent. Some context: Only have one FileField on the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, this is for historic purposes. The first models had no organization and were therefore at the root.
Unfortunately, for backwards compatibility purposes, it is now complicated to change the behavior.
Related: while working on the models’ data in https://observablehq.com/@huggingface/kaggle-dataset-huggingface-modelhub, I have been surprised that some of the "modelId"s are not “user/model”, but just “model” (I understand all of them are models provided by Hugging Face as the organization). eg: https://huggingface.co/bert-base-uncased