git clone failed with error: git-lfs: command not found
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 275
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 33
Description
➜ opensource git clone https://github.com/zhaohaidao/rtp-llm.git
Cloning into 'rtp-llm'...
remote: Enumerating objects: 41699, done.
remote: Counting objects: 100% (4237/4237), done.
remote: Compressing objects: 100% (290/290), done.
remote: Total 41699 (delta 4078), reused 3948 (delta 3947), pack-reused 37462 (from 1)
Receiving objects: 100% (41699/41699), 303.20 MiB | 5.60 MiB/s, done.
Resolving deltas: 100% (30182/30182), done.
git-lfs filter-process: git-lfs: command not found
fatal: the remote end hung up unexpectedly
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report only names the git clone command and the “git-lfs: command not found” checkout failure; start by reproducing the clone and checking the repository’s setup guidance for Git LFS. Done means the repository can be cloned and checked out without that failure, but no file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100