transformers - ✅(Solved) Fix Wrong checkpoint path in Dinov2 model_docs [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
huggingface/transformers#45431Fetched 2026-04-16 06:35:43
View on GitHub
Comments
0
Participants
1
Timeline
8
Reactions
0
Participants
Timeline (top)
mentioned ×3subscribed ×3closed ×1cross-referenced ×1

Fix Action

Fix / Workaround

The current checkpoint "google/dinov2-base-patch16-224" does not exist. The correct one should be "facebook/dinov-base".

PR fix notes

PR #45430: [Doc] Correct checkpoint path in Dinov2 model_docs

Description (problem / solution / changelog)

Fix checkpoint path in Dinov2 model_docs.

What does this PR do?

Fixes the wrong checkpoint path in Dinov2 model_docs #45431

Changes made: the previous checkpoint (google/dinov2-base-patch16-224) does not exist and has been changed to the correct one (facebook/dinov2-base).

<!-- Congratulations! You've made it this far! You're not quite done yet though. Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution. Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change. Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost. --> <!-- Remove if not applicable -->

Code Agent Policy

The Transformers repo is currently being overwhelmed by a large number of PRs and issue comments written by code agents. We are currently bottlenecked by our ability to review and respond to them. As a result, we ask that new users do not submit pure code agent PRs at this time. You may use code agents in drafting or to help you diagnose issues. We'd also ask autonomous "OpenClaw"-like agents not to open any PRs or issues for the moment.

PRs that appear to be fully agent-written will probably be closed without review, and we may block users who do this repeatedly or maliciously.

This is a rapidly-evolving situation that's causing significant shockwaves in the open-source community. As a result, this policy is likely to be updated regularly in the near future. For more information, please read CONTRIBUTING.md.

  • I confirm that this is not a pure code agent PR.

Before submitting

  • This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
  • Did you read the contributor guideline, Pull Request section?
  • Was this discussed/approved via a Github issue or the forum? Please add a link to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the documentation guidelines, and here are tips on formatting docstrings.
  • Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR. Below are people related to vision models and documentation: @yonigozlan @molbap @stevhliu

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @ If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**. Please tag fewer than 3 people. Models: - text models: @ArthurZucker @Cyrilvallez - vision models: @yonigozlan @molbap - audio models: @eustlb @ebezzam @vasqu - multimodal models: @zucchini-nlp - graph models: @clefourrier Library: - generate: @zucchini-nlp (visual-language models) or @gante (all others) - continuous batching: @remi-or @ArthurZucker @McPatate - pipelines: @Rocketknight1 - tokenizers: @ArthurZucker and @itazap - trainer: @SunMarc - attention: @vasqu @ArthurZucker @CyrilVallez - model loading (from pretrained, etc): @CyrilVallez - distributed: @3outeille @ArthurZucker - CIs: @ydshieh Integrations: - ray/raytune: @richardliaw, @amogkam - Big Model Inference: @SunMarc - quantization: @SunMarc - kernels: @drbh - peft: @BenjaminBossan @githubnemo Devices/Backends: - AMD ROCm: @ivarflakstad - Intel XPU: @IlyasMoutawwakil - Ascend NPU: @ivarflakstad Documentation: @stevhliu Research projects are not maintained and should be taken as is. -->

Changed files

  • src/transformers/models/dinov2/configuration_dinov2.py (modified, +3/-3)
RAW_BUFFERClick to expand / collapse

Wrong checkpoint path in Dinov2 model_docs.

The current checkpoint "google/dinov2-base-patch16-224" does not exist. The correct one should be "facebook/dinov-base".

This issue is fixed in PR #45430

Who can help?

@yonigozlan @molbap @stevhliu

Notes

This is a minor issue, but it might help new users. Thanks for your time and for maintaining such a great library.

extent analysis

TL;DR

Update the checkpoint path in the Dinov2 model_docs to "facebook/dinov-base" to fix the issue.

Guidance

  • Verify that the correct checkpoint path is used in the model_docs by checking the documentation for any references to the incorrect path "google/dinov2-base-patch16-224".
  • Update the checkpoint path to "facebook/dinov-base" in the relevant code or configuration files.
  • If possible, test the updated model_docs with the new checkpoint path to ensure it resolves the issue.
  • Consider applying the fix from PR #45430, if available, to ensure the issue is fully resolved.

Example

No code snippet is provided as the issue does not contain sufficient code context.

Notes

This fix assumes that the correct checkpoint path is indeed "facebook/dinov-base" and that updating the path will resolve the issue. If further issues arise, additional troubleshooting may be necessary.

Recommendation

Apply the workaround by updating the checkpoint path to "facebook/dinov-base", as this is a minor issue and the correct path is known.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING