Can't clone repo due to LFS account limit

[diarmidmackenzie]

Try to clone my fork of this repo, I get the following error:

Cloning into 'C:\Users\ASUS\Documents\GitHub\AframeCommunity\moonrider-test\moonrider'...
remote: Enumerating objects: 3059, done.        
remote: Counting objects: 100% (745/745), done.        
remote: Compressing objects: 100% (42/42), done.        
remote: Total 3059 (delta 715), reused 703 (delta 703), pack-reused 2314        
Receiving objects: 100% (3059/3059), 7.64 MiB | 6.22 MiB/s, done.
Resolving deltas: 100% (2133/2133), done.
Updating files: 100% (301/301), done.
Downloading assets/img/envmap.psd (604 KB)
Error downloading object: assets/img/envmap.psd (0837264): Smudge error: Error downloading assets/img/envmap.psd (0837264a7ea743565218b35ee8cd4f5b2244810963a2de0a3c2d75a84dc35553): 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 'C:\Users\ASUS\Documents\GitHub\AframeCommunity\moonrider-test\moonrider\.git\lfs\logs\20221217T163942.5440013.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: assets/img/envmap.psd: 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 :/'


Would you like to retry cloning ?

Retry doesn't work. Following the failed operation, I am left with source code downloaded, but the version history is all messed up and hence I'm not able to commit changes.

The cause of the error seems to be a problem with the parent repo (supermedium/moonrider), not my fork:
https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage

"Bandwidth and storage usage only count against the repository owner's quotas. In forks, bandwidth and storage usage count against the root of the repository network. Anyone with write access to a repository can push files to Git LFS without affecting their personal bandwidth and storage quotas or purchasing data packs. Forking and pulling a repository counts against the parent repository's bandwidth limit."

I don't understand why the repo woud be using LFS, as the asset causing the problem is only 604 KB.

Can it be fixed not to use LFS?

I'd like to be able to clone the repo to work further on performance investigations as per diarmidmackenzie#3

[diarmidmackenzie]

Turns out I can disable the LFS settings on my fork of the repo, and now I can clone it fine.

diarmidmackenzie@a2fbd32

Maybe there is some downside to this solution, but all seems OK so far...

[dmarcos]

yeah. I think you should be fine without LFS

[dmarcos]

I have to investigate what LFS bandwidth quota exactly means. This repo is not cloned a lot. gh-pages traffic perhaps count towards the quota.