-
Notifications
You must be signed in to change notification settings - Fork 1k
Null pointer panic on dep init #351
Comments
Oooh, that's a real, proper bug you found there. I'll have a look soon. Thanks! |
Ah ok, so, there's two bugs here. First, there's a problem with the parser; https://github.com/lucas-clemente/quic-go/blob/master/utils/_gen.go is causing it to misidentify that as a However, even though it's been dropped, there are still other internal packages that import it, which means the algorithm creating the transitive closure still tries to visit it. What's weird is that it seems like this case still should be covered. Clearly there's some bit of state I'm missing; I'll keep at it. |
Same issue for me:
|
@sheerun is the project you were working on when you encountered this panic public, so that I can replicate? While I'm pretty sure I know the problem here, it would be good to be certain. |
+1 to replication steps - have heard about this a lot but have never had a good recipe to attempt to create it |
export GOPATH=$HOME/debug && go get -u github.com/golang/dep/... && go get -d github.com/ginuerzh/gost && cd $GOPATH/src/github.com/ginuerzh/gost/cmd/gost && dep init |
This is likely at least part of the problem - see #193. |
FWIW, I was about to comment on this issue and paste a log output of my own just before I realized I had messed up updating my previously installed copy of dep: I did Not sure if the other reporters actually did the same mistake, but just in case I thought I'd share. :-) |
i think this panic should be unreachable now - but it still exists because we only band-aid-ed over it, rather than fixing the underlying problem with the model. |
I was running
dep init
for the first time on a Caddy server plugin.The text was updated successfully, but these errors were encountered: