-
Notifications
You must be signed in to change notification settings - Fork 112
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
[BUG] git clone issue on newest Git version #1611
Comments
My proposal:
|
@MaheshRKumawat will take this |
I worked on this together with @MaheshRKumawat . The issue is not present anymore, so we encourage existing PRs to rerun the unit test: What happened?We were running on an ubuntu
This explains why the issue does not longer exists. For reference, here an example of the failing unit tests: Git Resource Some tests mutate or depend on git configurations. They must run sequentially to avoid race-conditions. Test that require git configurations cloning repositories with Git Large File Storage [It] should Git clone a repository to the specified target directory
/home/runner/work/build/build/cmd/git/main_test.go:502
[FAILED] Unexpected error:
<*main.ExitError | 0xc000341080>:
fatal: active `post-checkout` hook found during `git clone`:
/tmp/git3063540752/.git/hooks/post-checkout
For security reasons, this is disallowed by default.
If this is intentional and the hook should actually be run, please
run the command again with `GIT_CLONE_PROTECTION_ACTIVE=false`
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/' (exit code 128)
{ |
Is there an existing issue for this?
Kubernetes Version
No response
Shipwright Version
No response
Current Behavior
Git recently introduced new security features that prevent hooks to be automatically invoked during
git clone
. This affects git-lfs, see git-lfs/git-lfs#5749. As a consequence, our unit tests that use git-lfs are also broken. See https://github.com/shipwright-io/build/actions/runs/9250581194/job/25446913912?pr=1610#step:5:38.Expected Behavior
git-lfs should be functional
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: