-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
Hi @dwalintukan! Sorry about that, we'll solve it ASAP. If not tomorrow early next week. |
Appreciate the quick response and fix 🙏 @dmorn |
In the meanwhile you can set the environment variable |
Hey @dwalintukan! I think it's all set. Probably you also need to |
Hi @dmorn good news is the issue from But, ran into the same problem in * 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. |
When fetching the deps for our Elixir app
mix deps.get
in our Github Actions CI/CD, we have been getting these errors recently:This is our mix file:
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!
The text was updated successfully, but these errors were encountered: