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

Error when cloning with LFS objects #8

Open
HaHeho opened this issue Dec 7, 2023 · 0 comments
Open

Error when cloning with LFS objects #8

HaHeho opened this issue Dec 7, 2023 · 0 comments

Comments

@HaHeho
Copy link

HaHeho commented Dec 7, 2023

I tried a git pull after the two recent commits. The pull, failed and I didn't pay much attention to fixing it. I removed the entire directory and restarted with a fresh clone, resulting in the following error.

git clone https://github.com/polarch/Spherical-Harmonic-Transform.git
Cloning into 'Spherical-Harmonic-Transform'...
remote: Enumerating objects: 146, done.
remote: Counting objects: 100% (16/16), done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 146 (delta 4), reused 9 (delta 2), pack-reused 130
Receiving objects: 100% (146/146), 1.25 MiB | 3.37 MiB/s, done.
Resolving deltas: 100% (70/70), done.
Downloading Gaunt_matrices_30_30_30_sparse.mat (291 MB)
Error downloading object: Gaunt_matrices_30_30_30_sparse.mat (73d84a6): Smudge error: Error downloading Gaunt_matrices_30_30_30_sparse.mat (73d84a6ed72dcba68cc21b027768185fe6d975a77a1e335ab35fef8e9185908a): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

Errors logged to 'Spherical-Harmonic-Transform/.git/lfs/logs/20231207T203923.679184.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: Gaunt_matrices_30_30_30_sparse.mat: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

I'm unsure if this was also causing the issue when doing git pull on an existing clone. Either way, this may hinder a lot of people who are interested in your valuable repo! :)

My first impression from quickly looking up the error is that this is a minor misconfiguration of the repository, which can be fixed in the repo settings on GitHub, i.e., it requires your intervention. However, I don't have experience with LFS so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant