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/vet: inconsistent import #16027
Comments
Note that |
@OneOfOne can you share the package source code that triggers the panic? |
More specifically, can you please reduce this to a simple, non-proprietary example that isolates the problem? |
I'll try, but I'm not even sure which file is causing it, mainly because we don't have anything with those imports. |
I tried to isolate it as much as possible but I can't make a reproducible case. I hunted down the internal packages causing it (2 of them) but there's nothing weird in them, go 1.6's vet works as expected, golint doesn't say anything weird. I'll look more into it after work today. |
@OneOfOne This may be due to installed packages compiled by different versions of the compiler - we had this bug in the past and I've fixed it (at least the instance we've seen so far). Can you reproduce it? If so, can you try to re-compile everything with the latest compiler (1.7 beta) and see if you can still reproduce it? Thanks. |
@griesemer I coulda swore I nuked /pkg/ before I tested but I was wrong, it works now, I'll close this. |
I just got bit by this. Just like the OP, I have no clue why this is or where, but it definitely happens in my workspace, when I was working on peco/peco@c74a783 I'm using
|
@lestrrat As you say yourself, you appear to have outdated packages. Make sure they are compiled with the latest compiler and see if the problem persists. If it does, please open a new issue with detailed instructions how to recreate the issue. Thanks. |
okay, that works for me. thanks. I will check it out later when I get to work. If it's being caused by outdated installed packages and deleting them causes this issue to go away, it's working as intended, yes? (Update: yep, nuking my $GOPATH/pkg did the trick) |
@lestrrat Yes. A prior version used to have a bug in the new exporter/importer (the compiler's phases which write and read a package's exported interface). That bug has been fixed a while back, but it you have installed packages that were built using the buggy version, you run into this problem). |
Please answer these questions before submitting your issue. Thanks!
go version
)?go version devel +8042bfe 2016-06-10 01:00:09 +0000 linux/amd64
go env
)?Arch Linux 64bit
go vet ./...
The text was updated successfully, but these errors were encountered: