-
Notifications
You must be signed in to change notification settings - Fork 90
fix: normalize hf.co to huggingface.co to prevent duplicate models #614
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
fix: normalize hf.co to huggingface.co to prevent duplicate models #614
Conversation
When pulling models from HuggingFace, users can use either hf.co or huggingface.co as the domain. Previously, these were treated as different sources, causing the same model to be stored twice with different tags. This change normalizes hf.co URLs to huggingface.co in the normalizeModelName function, ensuring that: - hf.co/org/model and huggingface.co/org/model are treated as the same - Models are not pulled/stored twice when using different URL formats Fixes docker#609
Summary of ChangesHello @littleKitchen, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request resolves an issue where models from HuggingFace could be inadvertently duplicated in the system's storage. By introducing a normalization step for HuggingFace URLs, the system now consistently recognizes models regardless of whether they are referenced using the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request correctly normalizes hf.co URLs to huggingface.co to prevent duplicate model storage. The implementation is straightforward and includes relevant test cases. I've suggested a minor refinement to improve code efficiency and style. Overall, this is a good fix.
| if strings.HasPrefix(model, "hf.co/") { | ||
| model = "huggingface.co/" + strings.TrimPrefix(model, "hf.co/") | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For better performance and to make the code more idiomatic, you can use strings.CutPrefix. It combines strings.HasPrefix and strings.TrimPrefix into a single call, avoiding scanning the string for the prefix twice.
Additionally, consider defining "hf.co/" and "huggingface.co/" as package-level constants to improve maintainability, as they are used in multiple functions within this file (isHuggingFaceReference, parseHFReference).
| if strings.HasPrefix(model, "hf.co/") { | |
| model = "huggingface.co/" + strings.TrimPrefix(model, "hf.co/") | |
| } | |
| if newModel, found := strings.CutPrefix(model, "hf.co/"); found { | |
| model = "huggingface.co/" + newModel | |
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this, @littleKitchen
Could you use strings.CutPrefix as suggested by Gemini? 🙏
I’ve already approved it since it looks good to go.
While testing your changes, I noticed that we don’t check the local store before pulling from Hugging Face, so the model gets pulled again even when using the exact same reference. I’ll open a new issue for that, if you want to work on it, it’s all yours!
Updated: Added the issue here
|
Thanks for the review! Will update to use strings.CutPrefix. And yes, will work on #616 |
|
Done! |
Summary
Fixes #609
When pulling models from HuggingFace, users can use either
hf.coorhuggingface.coas the domain prefix. Previously, these were treated as different sources, causing the same model to be pulled and stored twice with different tags:Changes
hf.co/URLs tohuggingface.co/in thenormalizeModelNamefunctionResult
After this change, both URL formats resolve to the same canonical form:
hf.co/org/model→huggingface.co/org/model:latesthuggingface.co/org/model→huggingface.co/org/model:latestThis ensures models are not duplicated regardless of which URL format the user uses.