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

Github Actions CI/CD failing when trying to pull test fixture #8

Open
dwalintukan opened this issue Mar 6, 2024 · 5 comments
Open

Comments

@dwalintukan
Copy link

When fetching the deps for our Elixir app mix deps.get in our Github Actions CI/CD, we have been getting these errors recently:

remote: Total 881 (delta 35), reused 53 (delta 25), pack-reused 801        
origin/HEAD set to main
Downloading test/fixtures/mpeg-ts/stream.m3u8 (350 B)
Error downloading object: test/fixtures/mpeg-ts/stream.m3u8 (31fbfcd): Smudge error: Error downloading test/fixtures/mpeg-ts/stream.m3u8 (31fbfcd0960e77c53e9b7d406dff805498ba5076454c7f729e59261696b05cbe): 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/runner/work/stream-vortex/stream-vortex/deps/membrane_hls_plugin/.git/lfs/logs/20240306T182327.589032612.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: test/fixtures/mpeg-ts/stream.m3u8: smudge filter lfs failed
** (Mix) Command "git --git-dir=.git checkout --quiet origin/HEAD" failed

This is our mix file:

...
{:membrane_hls_plugin, github: "loopsocial/membrane_hls_plugin"},
{:membrane_mpeg_ts_plugin, github: "kim-company/membrane_mpeg_ts_plugin"},
...

Is it possible you are over your Git LFS quota for the month? Our CI/CD used to work a few weeks back, but recently stopped working. All of our CI/CD workflows are failing because of this. Could you please check if this is something that you can resolve on your end?

Also note we have tried to fork your repo and reference that, but it gives the same error. Thank you!

@dmorn
Copy link
Member

dmorn commented Mar 6, 2024

Hi @dwalintukan! Sorry about that, we'll solve it ASAP. If not tomorrow early next week.

@dwalintukan
Copy link
Author

Appreciate the quick response and fix 🙏 @dmorn

@philipgiuliani
Copy link
Contributor

In the meanwhile you can set the environment variable GIT_LFS_SKIP_SMUDGE=1 to skip LFS. The dependency will still work as we just use it for tests.

@dmorn
Copy link
Member

dmorn commented Mar 7, 2024

Hey @dwalintukan! I think it's all set. Probably you also need to mix deps.update kim_hls. Eventually we'll publish on hex.pm when the API is considered stable. Some changes have been done, in particular HLS.FS* modules do not exist anymore. The protocols have been moved to Membrane.HLS.{Reader, Writer}. Let me know how it goes!

@dwalintukan
Copy link
Author

dwalintukan commented Mar 11, 2024

Hi @dmorn good news is the issue from kim_hls is fixed! Thank you for the quick fix!

But, ran into the same problem in kim_mpeg_ts 😞 Do you want me to open an issue there as well?

* Getting kim_mpeg_ts (https://github.com/kim-company/kim_mpeg_ts.git)
...
Downloading docs/MPEG_transport_stream.pdf (481 KB)
Error downloading object: docs/MPEG_transport_stream.pdf (3a945d4): Smudge error: Error downloading docs/MPEG_transport_stream.pdf (3a945d449d335b8765da0c275b3d8eec0cf60f90f563322f403da5936c078e5f): 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/runner/work/stream-vortex/stream-vortex/deps/kim_mpeg_ts/.git/lfs/logs/20240311T204303.095253187.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: docs/MPEG_transport_stream.pdf: smudge filter lfs failed
** (Mix) Command "git --git-dir=.git checkout --quiet 3e3b160b95fa4392201d9ba83b24b27537883c17" failed
Error: Process completed with exit code 1.

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

3 participants