Skip to content
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

Unable to migrrate repos from Hugging Face #33453

Closed
Redstone1024 opened this issue Jan 31, 2025 · 4 comments · Fixed by #33454
Closed

Unable to migrrate repos from Hugging Face #33453

Redstone1024 opened this issue Jan 31, 2025 · 4 comments · Fixed by #33454
Labels

Comments

@Redstone1024
Copy link

Description

When I try to migrate a Hugging Face repo with LFS, I get the following error on Web:

StoreMissingLfsObjectsInRepository: "ref.name" is not allowed to be empty

But, the migration can be successful without LFS.

The test repo is: https://huggingface.co/deepseek-ai/DeepSeek-R1-Distill-Qwen-1.5B.

Related forum questions: https://forum.gitea.com/t/unable-to-migrrate-repos-from-hugging-face/10491.

Gitea Version

1.23.1

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I'm using a official Docker container running on Debian and https://demo.gitea.com has the same error.

Database

None

@wxiaoguang
Copy link
Contributor

Related to In some lfs server implementations, they require the ref attribute. #32838

@wxiaoguang
Copy link
Contributor

-> Revert empty lfs ref name #33454

GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Jan 31, 2025
wxiaoguang added a commit that referenced this issue Jan 31, 2025
Backport #33454 by wxiaoguang

Fix #33453

Co-authored-by: wxiaoguang <[email protected]>
@wxiaoguang
Copy link
Contributor

1.23-nightly is ready (it is a stable release and will be 1.23.2 soon), could you try whether there is still any problem?

@Redstone1024
Copy link
Author

1.23-nightly is ready (it is a stable release and will be 1.23.2 soon), could you try whether there is still any problem?

No problem, the error is fixed, thank you.

project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants