-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: go get -u: panic: runtime error: slice bounds out of range #16167
Comments
Can you make this crash without changes to cmd/go? Otherwise this bug report can be read as "if I modify the cmd/go binary, I can make it crash", which is less compelling of a bug report than if you can crash it unmodified. |
The exact same repro steps work with an unmodified go 1.6.1 binary, and it panics. It does not crash with an unmodified go 1.7 beta binary, but it does not clone the vendor submodules either. |
I am able to reproduce the panic with current HEAD. |
I can't reproduce this. I'm trying:
and I get:
I've tried go1.6, go1.7, and current master. What am I doing wrong? |
I did get #15201 to reproduce though. Maybe that's enough. |
CL https://golang.org/cl/31665 mentions this issue. |
What version of Go are you using (
go version
)?This also happens with go 1.6: cmd/go: go get panic: runtime error: slice bounds out of range #14826 (comment)
Verified against git master, but using a custom binary patched to workaround cmd/go: go 1.7 get does not clone git submodules #16165 with go 1.7 beta, which breaks git submodule clones. The issue above contains the complete diff that I used.
What operating system and processor architecture are you using (
go env
)?What did you do?
Run
go get -u
against a repo that is missing some git submodules:The original scenario for this was running the initial
go get
with missing SSH keys, causing the submodule clone to fail, and then re-runninggo get -u
to fetch the missing submodules.What did you expect to see?
I would expect go get to clone the missing submodules.
What did you see instead?
Go get panics, after succesfully cloning the missing vendor submodule:
The text was updated successfully, but these errors were encountered: