Unity-Technologies
can't clone the repository due to git LFS budget
It seems the issue comes from the current upstream repo's account, as reported here : https://github.com/atteneder/glTFast/issues/771#issue-3062796071
Hi,
do you have any problem cloning from this fork/repository?
git clone [email protected]:Unity-Technologies/com.unity.cloud.gltfast.git
yes, indeed :
Cloning into 'com.unity.cloud.gltfast'...
remote: Enumerating objects: 16293, done.
remote: Counting objects: 100% (4844/4844), done.
remote: Compressing objects: 100% (560/560), done.
remote: Total 16293 (delta 4514), reused 4284 (delta 4284), pack-reused 11449 (from 2)
Receiving objects: 100% (16293/16293), 4.42 MiB | 7.81 MiB/s, done.
Resolving deltas: 100% (12842/12842), done.
Updating files: 100% (2072/2072), done.
Downloading Packages/com.unity.cloud.gltfast.tests/Assets~/Khronos/AnimatedMorphCube/glTF-Quantized/AnimatedMorphCube.bin (1.7 KB)
Error downloading object: Packages/com.unity.cloud.gltfast.tests/Assets~/Khronos/AnimatedMorphCube/glTF-Quantized/AnimatedMorphCube.bin (bde22d0): Smudge error: Error downloading Packages/com.unity.cloud.gltfast.tests/Assets~/Khronos/AnimatedMorphCube/glTF-Quantized/AnimatedMorphCube.bin (bde22d01f34dd8f5d83cfbb20a1a6d117ec48596157df5d484a58eba13cdff51): batch response: This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access.
Errors logged to '/Users/ndvx/code/5gmag/com.unity.cloud.gltfast/.git/lfs/logs/20250514T151349.973011.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: Packages/com.unity.cloud.gltfast.tests/Assets~/Khronos/AnimatedMorphCube/glTF-Quantized/AnimatedMorphCube.bin: 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 opened a formal ticket on github support for clarification. See the note on forks here : https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage#about-billing-for-git-large-file-storage
We do have LFS budget allocated to our fork repo, but that doesn't seem to help.
I used to pay on a monthly basis for Git LFS packages on Github for my private account. I just noticed the billing changed. While I don't think this error involves my private account, maybe billing changed for the Unity org as well and that's the problem? I'll have to investigate.
It seems like the Git LFS traffic is indeed billed at the root repository, which is my personal account. I setup a reasonable budget for it. Could you please try if it works now?
@atteneder - thanks a lot for handling this promptly. I confirm it resolved it for us. I also wasn't expecting it to be billed on upstream. I guess the only way to not have LFS charged on upstream is to detach the forks, but that's something only the account maintaining the forks are entitled to do.
Thanks you both! We had indeed the same issue in the 5G-MAG repos. Somehow the regular bill for May hasn't come and instead we need to setup now budgets
