search

actions / checkout

Action for checking out a repo
https://github.com/features/actions
MIT License
5.76k stars 1.7k forks source link

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

Open leongross opened 2 hours ago

leongross commented 2 hours ago

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 commented 2 hours ago

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 commented 2 hours ago

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