-
Notifications
You must be signed in to change notification settings - Fork 38
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 error since using opam 2.3.0 #895
Comments
i was able to reproduce by forking the repository. I've added some debug variables and i ended up with:
From that it looks like the error doesn't actually come from either ocaml-setup or opam but a corruption of git-lfs file or some kind of issue accessing that file inside of the github action. I'm not sure why that would be the case. Does anyone have an idea? |
Thanks a lot for looking into this! I had no idea the repository even had something in LFS (I never even set it up myself because I never looked at that .gif file locally). The .gif opens on GitHub website at least, so it still seems to exist somewhere. Perhaps this opam 2.3.0 change is somehow related:
Maybe it always failed, but that failure was somehow swallowed like submodule updates before? Either way, seems like neither ocaml-setup nor opam is really the issue here. Perhaps the GitHub Action just needs some extra permissions to access LFS for the repository or something. |
the failure doesn't happen during the git submodule step and opam only calls git submodule when a I found a way to fix your problem but it's bringing more questions than answering them: kit-ty-kate/ocamlearlybird@2d20030. The only other thing git related that changed in 2.3 is that we're not using shallow clones anymore (it was causing issues with reproducibility) so maybe the fact that it's trying to unshallow-clone a shallow-cloned repository (the default github checkout action does a shallow clone from what i understand) is a causing issue. But then how did it work with 2.1 which has the same behaviour as 2.3 |
answering to my own question: i just tried using setup-ocaml@v2 which uses 2.1.6 and the same error appears but it delayed from the pin to the install command and there it looks like it's a non-fatal error. So the reason it worked with 2.1 is an accident (bug). Nonetheless i'll open a ticket in opam to at least improve the error message which is quite misleading and maybe we can find a git-lfs setting that makes it work out of the box. In the meantime the |
Tonight, I suppose due to #894 all jobs in one repository started failing with:
In a different repository, I have no issues, so I'm not entirely sure if setup-ocaml or opam itself is at fault.
The text was updated successfully, but these errors were encountered: