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

checkout@v4: remote: git: 'lariat' is not a git command #1916

Open
leongross opened this issue Sep 25, 2024 · 3 comments
Open

checkout@v4: remote: git: 'lariat' is not a git command #1916

leongross opened this issue Sep 25, 2024 · 3 comments

Comments

@leongross
Copy link

In the u-root project we use (presumably) the latest version of checkout@v4 in our CI. The CI failed once with the following error:

 remote: git: 'lariat' is not a git command. See 'git --help'.        
  remote: aborting due to possible repository corruption on the remote side.
  Error: fatal: protocol error: bad pack header
  The process '/usr/bin/git' failed with exit code 128
  Waiting 13 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +fa57918e80ab835d92553a72110f9e56adcd43f1:refs/remotes/pull/3111/merge
  remote: git: 'lariat' is not a git command. See 'git --help'.        
  remote: aborting due to possible repository corruption on the remote side.
  Error: fatal: protocol error: bad pack header
  The process '/usr/bin/git' failed with exit code 128
  Waiting 10 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +fa57918e80ab835d92553a72110f9e56adcd43f1:refs/remotes/pull/3111/merge
  remote: git: 'lariat' is not a git command. See 'git --help'.        
  remote: aborting due to possible repository corruption on the remote side.
  Error: fatal: protocol error: bad pack header
  Error: The process '/usr/bin/git' failed with exit code 128

After re-running the ci (more precisely git commit --amend --no-edit && git push -f)

@doowb
Copy link

doowb commented Sep 25, 2024

I came here because I'm getting the exact same error in a workflow that's triggered by a cron schedule. The run that ran 1 hour earlier was successful using the same git fetch command and sha. Could this be on GitHub's server side?

/edit: just found this: https://www.githubstatus.com/incidents/q3xqwmcxzkqq

@alynn-coefficient
Copy link

Appears to be a symptom of this incident: https://www.githubstatus.com/incidents/q3xqwmcxzkqq

@leongross
Copy link
Author

The issue seems to be resolved, but it seems as if there was some race condition that should be fixed, so I keep this issue open.

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