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

Git LFS files are exceeding Git LFS data bandwidth limit #177

Open
scp93ch opened this issue Jun 3, 2024 · 0 comments
Open

Git LFS files are exceeding Git LFS data bandwidth limit #177

scp93ch opened this issue Jun 3, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@scp93ch
Copy link
Member

scp93ch commented Jun 3, 2024

I received an email from GitHub on 28/5 pointing out that we had reached the Git LFS data bandwidth for the month. It is not clear to me what the consequences of that were. It seems likely that we need to get rid of all or some of the LFS data from the system-modeller repo.

On the free plan (https://github.com/organizations/Spyderisk/settings/billing/summary) we have 1GB monthly LFS bandwidth.

The files we have are:

$ git lfs ls-files
444dd43666 * src/main/resources/static/css/fonts/FontAwesome.otf
7bfcab6db9 * src/main/resources/static/css/fonts/fontawesome-webfont.eot
aa58f33f23 * src/main/resources/static/css/fonts/fontawesome-webfont.ttf
ba0c59deb5 * src/main/resources/static/css/fonts/fontawesome-webfont.woff
2adefcbc04 * src/main/resources/static/css/fonts/fontawesome-webfont.woff2
2d8bf5adff * src/test/resources/StoreTest/A.rdf
0b866e15b4 * src/test/resources/StoreTest/domain-shield.rdf
fa09b48bd3 * src/test/resources/semanticstore/bm25.rdf
923ebcb8db * src/test/resources/semanticstore/bm5.rdf
150c7025d3 * src/test/resources/semanticstore/bm50.rdf
2d63bb242c * src/test/resources/semanticstore/core.rdf
aba333df9d * src/test/resources/semanticstore/domain-assured.rdf
51847ac99a * src/test/resources/semanticstore/generic.rdf

The sizes are:

$ git lfs ls-files | cut -d' ' -f3 | xargs ls -lh
-rw-r--r-- 1 scp scp 132K Mar 31  2023 src/main/resources/static/css/fonts/FontAwesome.otf
-rw-r--r-- 1 scp scp 162K Mar 31  2023 src/main/resources/static/css/fonts/fontawesome-webfont.eot
-rw-r--r-- 1 scp scp 162K Mar 31  2023 src/main/resources/static/css/fonts/fontawesome-webfont.ttf
-rw-r--r-- 1 scp scp  96K Mar 31  2023 src/main/resources/static/css/fonts/fontawesome-webfont.woff
-rw-r--r-- 1 scp scp  76K Mar 31  2023 src/main/resources/static/css/fonts/fontawesome-webfont.woff2
-rw-r--r-- 1 scp scp 1.4K Mar 31  2023 src/test/resources/StoreTest/A.rdf
-rw-r--r-- 1 scp scp 627K Mar 31  2023 src/test/resources/StoreTest/domain-shield.rdf
-rw-r--r-- 1 scp scp  29K Mar 31  2023 src/test/resources/semanticstore/bm25.rdf
-rw-r--r-- 1 scp scp 3.7K Mar 31  2023 src/test/resources/semanticstore/bm5.rdf
-rw-r--r-- 1 scp scp  56K Mar 31  2023 src/test/resources/semanticstore/bm50.rdf
-rw-r--r-- 1 scp scp 452K Mar 31  2023 src/test/resources/semanticstore/core.rdf
-rw-r--r-- 1 scp scp 762K Mar 31  2023 src/test/resources/semanticstore/domain-assured.rdf
-rw-r--r-- 1 scp scp 2.1M Mar 31  2023 src/test/resources/semanticstore/generic.rdf

We don't need to commit the Font Awesome files to the repo, they can be linked to online resources in the webapp.

The various RDF files were at some point made into LFS files because the serialisation of RDF from Protege was in a random order so the files did not diff sensibly and so it was easier to just put them in LFS. There is no reason I can see to keep them in LFS now - those files do not change.

The question is, how do we get rid of them so that they do not use any bandwidth? The docs are not clear: https://docs.github.com/en/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage

Do we need to purge them from the git history as well? Perhaps if we remove them from HEAD then they won't be downloaded when someone clones the repo and that would be good enough?

@kenmeacham kenmeacham added the bug Something isn't working label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants