-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: panic when loading a module from svn #28943
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
Comments
Running
|
/cc @bcmills Panics even in 1.11, although with a different error.
go: finding llvm.org/llvm/bindings/go/llvm latest
panic: runtime error: slice bounds out of range
goroutine 432 [running]: Tentatively marking for 1.12. Feel free to punt. |
I can't reproduce this at head.
Do note the error midway through: |
@mewmew, can you verify whether this still reproduces for you at a more recent |
@bcmills, I still get a nil pointer defer it looks like: I cloned dannypsnl/elz@f1b9a0f to a directory outside of GOPATH and ran
|
I put a minimal reproducible example at https://github.com/mewspring/go-issue-28943 Edit: I also tried to remove
|
Ok, that one reproduces it for me. Thanks! |
Found the trouble, I think:
|
Perfect! |
Ah, the |
Change https://golang.org/cl/153458 mentions this issue: |
Change https://golang.org/cl/153459 mentions this issue: |
…functions and malformed responses Updates #28943 Updates #26092 Change-Id: I07af2731ef5af046b9f7c7280ccb3976cdf41ca4 Reviewed-on: https://go-review.googlesource.com/c/153458 Run-TryBot: Bryan C. Mills <[email protected]> Reviewed-by: Jay Conrod <[email protected]>
The panic should be fixed, but note that the code in question still won't build in module mode. (That's #26092, which I've left open.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Clone https://github.com/elz-lang/elz at rev dannypsnl/elz@f1b9a0f to outside of GOPATH, and the running
go install -v ./...
to build the packages of the module.What did you expect to see?
Successful compilation.
What did you see instead?
Compile time panic.
The text was updated successfully, but these errors were encountered: