# LLM model download fail
**URL:**
**Author:**  [@alice86](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Falice86)%5C
**Post date:** [August 20, 2024, 3:19am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fllm-model-download-fail%2F103078%2F1 "2024-08-20T03:19:47Z")
git clone [taide/Llama3-TAIDE-LX-8B-Chat-Alpha1 · Hugging Face](https://huggingface.co/taide/Llama3-TAIDE-LX-8B-Chat-Alpha1)
For security reasons, this is disallowed by default.
If this is intentional and the hook should actually be run, please
run the command again with `GIT_CLONE_PROTECTION_ACTIVE=false`
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with ‘git status’
and retry with ‘git restore --source=HEAD :/’
download model is so difficult
---
**Author:**  [@mahmutc](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmahmutc)%5C
**Post date:** [August 20, 2024, 8:08am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fllm-model-download-fail%2F103078%2F2 "2024-08-20T08:08:10Z")
Git version might be the issue:
>
>
> Git has recently released several security releases that introduce a regression …when using \`git clone\` on a repository with Git LFS. When cloning, a message like the following occurs, and LFS files are not checked out:
>
> \`\`\`
> $ git clone https://github.com/octocat/xyzzy.git
> Cloning into 'pull-bug'...
> remote: Enumerating objects: 1275, done.
> remote: Counting objects: 100% (343/343), done.
> remote: Compressing objects: 100% (136/136), done.
> remote: Total 1275 (delta 221), reused 327 (delta 206), pack-reused 932
> Receiving objects: 100% (1275/1275), 290.78 KiB | 2.88 MiB/s, done.
> Resolving deltas: 100% (226/226), done.
> Filtering content: 100% (504/504), 1.86 KiB | 0 bytes/s, done.
> fatal: active \`post-checkout\` hook found during \`git clone\`:
> /home/octocat/xyzzy/.git/hooks/post-checkout
> For security reasons, this is disallowed by default.
> If this is intentional and the hook should actually be run, please
> run the command again with \`GIT\_CLONE\_PROTECTION\_ACTIVE=false\`
> warning: Clone succeeded, but checkout failed.
> You can inspect what was checked out with 'git status'
> and retry with 'git restore --source=HEAD :/'
> \`\`\`
>
> Note that this message and the nonzero exit status also affect users using \`GIT\_LFS\_SKIP\_SMUDGE=1\`, such as many CI systems, so this can't be used as a workaround. Users can set the environment variable \`GIT\_CLONE\_PROTECTION\_ACTIVE=false\` globally, which will disable this check, or if the repository has already been cloned, users can use \`git lfs pull\` to fix the repository and the hooks. (Note that setting the \`GIT\_CLONE\_PROTECTION\_ACTIVE=false\` environment variable disables the defense-in-depth measure outlined below.)
>
> Ultimately, this is a regression in Git that was introduced as a defense-in-depth measure. The problem is in Git and cannot be worked around in Git LFS itself without a substantial loss of functionality. The Git developers are aware of the problem and discussion about how to solve it is underway or will be underway shortly \[on the mailing list\](https://git-scm.com/community). If you're interested, you can follow the discussion there or post yourself (please note that only \[plain text mail\](https://useplaintext.email/) is allowed; no HTML parts can be sent at all).
>
> We realize this has a big impact and we're working with the Git developers to get it fixed as quickly as possible. In the mean time, distributors and users can revert the following non-essential patches, which will solve the problem:
>
> \* clone: prevent hooks from running during a clone
> \* core.hooksPath: add some protection while cloning
>
> Since this is a Git bug and not a Git LFS bug, most discussion about this issue should take place on the Git list, and not on the Git LFS GitHub page. Please refrain from opening issues on this matter on the Git LFS issue tracker. If there is productive discussion about topics that aren't suitable for the Git list (e.g., workarounds), please discuss those in \[the Git LFS discussions\](https://github.com/git-lfs/git-lfs/discussions).
>
> We'd also like to encourage people to participate in the respective communities in a positive way and in conjunction with the \[Git LFS Code of Conduct\](https://github.com/git-lfs/git-lfs/blob/main/CODE-OF-CONDUCT.md) and \[the Git Code of Conduct\](https://github.com/git/git/blob/master/CODE\_OF\_CONDUCT.md).
>
>
> \### Description
>
> In the \[recent release \](https://github.com/actions/runner-im…ages/releases/tag/ubuntu24%2F20240516.4) you have upgrade the git version to 2.45.1.
> That upgrade leads to a huge problem, our workflows \*\*especially the ones uses GIT LFS\*\* start to fail due to following reason:
>
> \`\`\`
> │ exit code: 128
> ╰─\> \[9 lines of output\]
> fatal: active \`post-checkout\` hook found during \`git clone\`:
> /tmp/pip-req-build-81t\_gbyh/.git/hooks/post-checkout
> For security reasons, this is disallowed by default.
> If this is intentional and the hook should actually be run, please
> run the command again with \`GIT\_CLONE\_PROTECTION\_ACTIVE=false\`
> warning: Clone succeeded, but checkout failed.
> You can inspect what was checked out with 'git status'
> and retry with 'git restore --source=HEAD :/'
>
> \[end of output\]
> \`\`\`
>
> We have verified that we can disable it by assign \`GIT\_CLONE\_PROTECTION\_ACTIVE = False\` to each individual reusable workflow.
> However, we have so many workflows which relies on the different versions of reusable workflows that we can not go in and fix each individual of them.
>
>
> This breaking change was introduced by the new git version.
> Here is the relevant issue: https://github.com/git-lfs/git-lfs/issues/5749
> You have never warn customers in advance and caused huge problem at our company.
>
> This is against your promise in the README:
>
> \`\`\`
> For high impact changes, we will post these in advance to the GitHub Changelog on our blog and on twitter.
>
> Ex: breaking changes, GA or deprecation of images
> \`\`\`
>
> Please roll back the change to the Github Runners or try to downgrade the git version so that we can keep using github!
>
>
>
> \### Platforms affected
>
> \- \[\] Azure DevOps
> \- \[X\] GitHub Actions - Standard Runners
> \- \[\] GitHub Actions - Larger Runners
>
> \### Runner images affected
>
> \- \[X\] Ubuntu 20.04
> \- \[X\] Ubuntu 22.04
> \- \[X\] Ubuntu 24.04
> \- \[\] macOS 11
> \- \[\] macOS 12
> \- \[\] macOS 13
> \- \[\] macOS 13 Arm64
> \- \[\] macOS 14
> \- \[\] macOS 14 Arm64
> \- \[\] Windows Server 2019
> \- \[\] Windows Server 2022
>
> \### Image version and build link
>
> \[Ubuntu 20.04 (20240516) Image Update\](https://github.com/actions/runner-images/releases/tag/ubuntu20%2F20240516.1)
>
> \### Is it regression?
>
> Ubuntu 20.04 (20240514) Image Update
>
> \### Expected behavior
>
> We can checkout code as normal
>
> \### Actual behavior
>
> We can not checkout code because of the git setting.
>
> \### Repro steps
>
> Fetch a repo that has LFS object
Did you try to run `GIT_CLONE_PROTECTION_ACTIVE=false git clone https://huggingface.co/taide/Llama3-TAIDE-LX-8B-Chat-Alpha1`?
Otherwise you can try Hugging Face Client Library:
> **[Downloading models](https://huggingface.co/docs/hub/en/models-downloading)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.