Cloning the repo causes errors

[spessasus]

FluidSynth version

Not related

Describe the bug

It seems that adding the filter test files broke git clone:

git clone "https://github.com/fluidsynth/fluidsynth"
Cloning into 'fluidsynth'...
remote: Enumerating objects: 21711, done.
remote: Counting objects: 100% (1245/1245), done.
remote: Compressing objects: 100% (598/598), done.
remote: Total 21711 (delta 818), reused 1009 (delta 641), pack-reused 20466 (from 1)
Receiving objects: 100% (21711/21711), 10.58 MiB | 9.15 MiB/s, done.
Resolving deltas: 100% (16294/16294), done.
Downloading test/manual/awe32_nrpn/Altitude/Altitude-SB Audigy2 ZS.ogg (7.4 MB)
Error downloading object: test/manual/awe32_nrpn/Altitude/Altitude-SB Audigy2 ZS.ogg (9c4ded7): Smudge error: Error downloading test/manual/awe32_nrpn/Altitude/Altitude-SB Audigy2 ZS.ogg (9c4ded7fc02982d2239a830ad08b41ddeea6f5d6a081568cd073290695e322ce): 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 '/home/spessasus/Desktop/clutter/fluidsynth/.git/lfs/logs/20241125T151415.673716381.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: test/manual/awe32_nrpn/Altitude/Altitude-SB Audigy2 ZS.ogg: 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 :/'

Expected behavior

No errors when cloning, like previously.

Steps to reproduce

git clone "https://github.com/fluidsynth/fluidsynth"

Additional context

If this is not important, feel free to close it

[derselbst]

Which git versions are you using?

git-lfs --version
git --version

[spessasus]

git-lfs --version
git-lfs/3.5.1 (GitHub; linux amd64; go 1.22.1)
git --version
git version 2.47.0

[spessasus]

I have just pacman -Sy git to the latest version (2.47.1-1). The issue still persists. LFS already was using the latest version.

[derselbst]

Oh, I see. Not related to version.

...so by adding 60MB to LFS we've hit the 1GB / month bandwidth quota. That came unexpected. My best guess it that the CI builds have LFS check out enabled, I'll need to go through them.

[derselbst]

I don't see any CI build that has LFS checkout enabled. The bandwidth quota will reset in 15 days, I'd suggest we keep observing this to see if the bandwidth quota somehow correlates with the number of CI builds. If it doesn't, I'd simply outsource the test files into a dedicated repository without using LFS.