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
cmd/go: git remote did not send all necessary objects #59044
Comments
Can you show us the output of the |
Logs from CICD failing on two different branches. Note repo name is updated for privacy. Also note the CICD is v1.20.1 (not .2) Click to see logs
|
That's a git error, I don't think there's anything go can do about it |
@seankhliao maybe so, but why does it only happen with v1.20 then? Is the git command changed? |
the git commands go runs are in the log you posted, perhaps it was your git version that changed and not go? |
The CICD environment is unchanged apart from the goenv installed go version, here are the successful logs from v1.19 Click to see logs
|
Here are the git commands filtered
EDIT: |
I believe this may be related to local corruption of the caches somehow and will reopen if not |
After more investigation, I have ruled out any existing broken cache causing the problem. I have run It's like the git folder it is setting up the first time it is run is missing some information with v1.20 Here is a diff. Note the missing objects/pack files and shallow file in the broken one... Click to view folder diff of working vs not working
|
Running v1.19.7 vs v1.20.2
goget-v1.19.log - working fine There must be something in the structure of the folder that it creates for the repo so that it is different and fails for 1.20.2... anyone got any ideas? |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes - inconsistently
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Seems very similar to old issue #31399
Getting inconsistent results when running go get command on a CodeCommit git repo. In the form of:
go get -x git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/x.git@<branch>
The command fails inconsistently with
Using the local machine, switching the branch name sometimes got it to work. However, using our CICD pipeline the command seems to always fail no matter the branch.
It doesn't fail ever with go version 1.19 - so there doesn't appear to be a problem with the repository.
EDIT: also noting that the commit hash that it complains about is different on different branches that we try it on
What did you expect to see?
The command successfully completes which is the case when switching back to v1.19
What did you see instead?
did not send all necessary objects
The text was updated successfully, but these errors were encountered: