You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
We are using actions/checkoutv3 in our github action workflow and we have seen intermittent issues since yesterday.
The builds complete successfully some times, but not others and here is the error message when it fails:
Error: fatal: fetch-pack: invalid index-pack output
Error: The process '/usr/bin/git' failed with exit code 128
I have found related issues in other versions of checkout and also related to git itself, like this one here.
The weird thing is that this error is not consistent and it is happening on one specific workflow and not all the time.
The way we use checkout is the following:
We are using v3 and the depth depends on the case. If it is a PR we are using depth 300 and if it is a push to master we are fetching everything (depth 0).
Again, this has been working for months and now it has showed this error but not in all the builds.
The text was updated successfully, but these errors were encountered:
Hi!
We are using actions/checkoutv3 in our github action workflow and we have seen intermittent issues since yesterday.
The builds complete successfully some times, but not others and here is the error message when it fails:
Error: fatal: fetch-pack: invalid index-pack output
Error: The process '/usr/bin/git' failed with exit code 128
I have found related issues in other versions of checkout and also related to git itself, like this one here.
The weird thing is that this error is not consistent and it is happening on one specific workflow and not all the time.
The way we use checkout is the following:
We are using v3 and the depth depends on the case. If it is a PR we are using depth 300 and if it is a push to master we are fetching everything (depth 0).
Again, this has been working for months and now it has showed this error but not in all the builds.
The text was updated successfully, but these errors were encountered: