Git clone ... fails with error 422, service parameter is needed

I’m trying to get my first llm to run locally, just to learn a bit about things. I’ve got git-lfs installed and initialized. When trying to clone this happens:

git clone https://Humble_me:hf_my_read_token@huggingface.com/google/codegemma-2b-GGUF
Cloning into 'codegemma-2b-GGUF'...
remote: `service` parameter is needed
fatal: unable to access 'https://huggingface.com/google/codegemma-2b-GGUF/': The requested URL returned error: 422

I really don’t know what this service parameter is and how to pass it through.

Maybe a read toke isn’t enough for this? I don’t know where to look any further.

EDIT:
I found a seemingly unrelated post:

llm-model-download-fail

However it was mentioned in the replies that their version of git probably caused that issue. As my version was much older atgit version 2.34.1,I just upgraded to git version 2.49.0 which is the current one. This however didn’t make a difference.

1 Like

In the case of Windows, it’s usually because of the version of git.
This time, though, it doesn’t seem to be the case.

Even so, 422 errors with git are extremely rare.
It might be a bug in the site.

For Windows users

Thank you. I checked the stack-overflow question and my time-zone and time configuration are correct. Also in this case Firefox isn’t even involved as it’s git (this seemed to be a Firefox specific problem that didn’t occur with Chrome).

Git executed from command line as I’m running Linux.

What got me stumped from the stack-exchange contribution is the ‘change rejected’ bit as I’ve only got a read token. I just didn’t expect that I would need write access for this. Also it may me completely misleading as it was a problem with gitlab.

1 Like

I couldn’t find any examples of the 422 error on Hugging Face because it’s so rare, except for Inference API-related errors… sorry about that.

Although it’s not a 422 error, if a Fatal error occurs, it’s probably because the network connection itself isn’t working properly. In the case below, it seems that the IPv6 setting was the cause, but there are various other possibilities.

Ok. It’s rather embarrassing. I did following change:

huggingface.com

to

huggingface.co

Now I’m getting Error 403.

Your request to access model google/codegemma-2b-GGUF is awaiting a review from the repo authors.

However this was because I accepted before the terms for a h5 file and had to accept again for this gguf. Once done the download started.

Noob problems :zany_face:

1 Like

When you go with a web browser to https://huggingface.com you just get redirected to https://huggingface.co.

¡O, gloria inmarcesible!
¡O, júbilo inmortal!
En surcos de dolores,
el bien germina ya.

huggingface.com

lol😆

This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.