-
Notifications
You must be signed in to change notification settings - Fork 1k
panic: version queue is empty, should not happen #1799
Comments
I have a similar panic when I try to $ go version
go version go1.10.1 darwin/amd64
$ dep version
dep:
version : v0.4.1
build date : 2018-01-27
git hash : 37d9ea0
go version : go1.9.3
go compiler : gc
platform : darwin/amd64 $ dep ensure -update
panic: version queue is empty, should not happen
goroutine 1 [running]:
github.com/golang/dep/gps.(*solver).findValidVersion(0xc42030cc60, 0xc420677540, 0xc4206ab0c0, 0x1, 0x1, 0x0, 0xc4206ab0c0)
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/gps/solver.go:927 +0x53f
github.com/golang/dep/gps.(*solver).createVersionQueue(0xc42030cc60, 0xc420204740, 0x14, 0x0, 0x0, 0xc4206ab0c0, 0x1, 0x1, 0x0, 0x0, ...)
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/gps/solver.go:914 +0x955
github.com/golang/dep/gps.(*solver).solve(0xc42030cc60, 0x17e7e40, 0xc4200160a0, 0x1, 0xc42030af00, 0xc42030af60)
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/gps/solver.go:517 +0x5b0
github.com/golang/dep/gps.(*solver).Solve(0xc42030cc60, 0x17e7e40, 0xc4200160a0, 0x1843a90, 0xc42001e034, 0x1d, 0xc4202f8300)
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/gps/solver.go:457 +0xe4
main.(*ensureCommand).runUpdate(0xc420159f06, 0xc42005d080, 0xc42000e1d0, 0x0, 0x0, 0xc42005d0e0, 0x17eb320, 0xc42005d6e0, 0xc42001e004, 0x4d, ...)
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/cmd/dep/ensure.go:389 +0x2c0
main.(*ensureCommand).Run(0xc420159f06, 0xc42005d080, 0xc42000e1d0, 0x0, 0x0, 0x0, 0x0)
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/cmd/dep/ensure.go:218 +0x838
main.(*Config).Run(0xc42005cf60, 0xc42005cf60)
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/cmd/dep/main.go:210 +0x11cb
main.main()
/private/tmp/dep-20180127-69957-1mynnnl/src/github.com/golang/dep/cmd/dep/main.go:52 +0x1fc |
Same issue for me. This occurs on a
|
Added some extra debugging, and for me this is the call causing the failure:
It looks like it has something to do with the |
Same issue here, also caused by |
The same thing:
|
Seems to be solved by specifying [[constraint]]
source = "https://github.com/fsnotify/fsnotify/archive/v1.4.7.tar.gz"
name = "gopkg.in/fsnotify.v1" I may be wrong (most likely), but I think the problem in different pathes to
|
I've specified
|
Thanks for the tip -- specifying the source for fsnotify did indeed fix the issue. Here's the constraint I used for the repo, which updates the source for the repo itself rather than tying it to a specific version:
|
@Pcyeol as specified in the warning message at the top of your run, the constraint is not used because you don't have You either need to add |
@nmiyake It finally works! Sorry for this mistake. Thanks! |
I received the exact same error as everyone else though the problem for me stemmed from the fact that a dependency was only in Output before I pushed the new dependency.
Output after pushing into `github.com/cheapRoc/grpc-zerolog`.
It is possible this is an entirely different issue but logging here since it has the same error message. |
We're about to install some new packages which will not play nicely with the versions we've currently got in Gopkg.lock. Updating in preparation. Note that we had to add a workaround to Gopkg.toml for golang/dep#1799.
We're about to install some new packages which will not play nicely with the versions we've currently got in Gopkg.lock. Updating in preparation. Note that we had to add a workaround to Gopkg.toml for golang/dep#1799.
This introduced some new dependencies, namely fsnotify, which dep has trouble with. So I applied the workaround from golang/dep#1799.
This introduced some new dependencies, namely fsnotify, which dep has trouble with. So I applied the workaround from golang/dep#1799.
I think it's better.
|
This finally worked if someone is still having issues: EDIT Nevermind, Had to change to
I am on 0.5.0
|
It's been necessary to add a dep override for fsnotify to avoid a dep panic as detailed here: golang/dep#1799
Include fsnotify because of golang/dep#1799
This is a workaround for golang/dep#1799. Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
Handles also golang/dep#1799
Handles also golang/dep#1799
Handles also golang/dep#1799
dep ensure issue in golang/dep#1799
vendoring azure-sdk-for-go the azure sdk requires fsnotify to be overriden ref: golang/dep#1799
vendoring azure-sdk-for-go the azure sdk requires fsnotify to be overriden ref: golang/dep#1799
I saw the same
My
|
vendoring azure-sdk-for-go the azure sdk requires fsnotify to be overriden ref: golang/dep#1799
golang/dep#1799 Signed-off-by: Andrew Edstrom <aedstrom@pivotal.io>
* Change in Elastic mapping caching was necessary as Elastic 7.* is dropping support for type specificiation and _doc is used implicitly and by default. Implementation was altered in a way that both 6.* and 7.* will still be supported. This is also handling the deprecation warning which was present since 6.8 and 7.*. See https://www.elastic.co/guide/en/elasticsearch/reference/master/removal-of-types.html * Updateable Go packages were updated. This doesn't affect Goa which remained on the version 1.2.1 and will require more time to update to the latest version. * Update caused extra "AllowNativePasswords" parameter to be configured within MySQL configuration in both Segments and Tracker. * Update also caused an extra override of "gopkg.in/fsnotify.v1" in Gopkg.toml which fixed panic within "dep ensure" command. See golang/dep#1799 (comment). * Index creation in Elastic docker image now creates all indices (some of them were omitted before)
There seems to be a specific dependency resolution bug in dep that's explored in golang/dep#1799. We've seen it every so often on our development machines. This commit introduces a suggested workaround for the problem, which seems to work on my box.
There seems to be a specific dependency resolution bug in dep that's explored in golang/dep#1799. We've seen it every so often on our development machines. This commit introduces a suggested workaround for the problem, which seems to work on my box.
This is a workaround for golang/dep#1799. Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
I am receiving this error too when doing a Error:
Dep Info:
Go Info:
|
* "dep ensure" won't work if this is not present. Seeing error: "panic: version queue is empty, should not happen" golang/dep#1799 (comment)
Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks! |
I'm working on a branch instead of master on bitbucket.org, I have up to date with this branch but still has this issue. When I switch on the master branch and deleted all the vendor things tried to regenerate, it turned out with the same issue.
What version of
dep
are you using (dep version
)?dep version
What
dep
command did you run?dep init -v
What did you expect to see?
Generate Gopkg.toml, Gopkg.lock, and vendor/
What did you see instead?
The text was updated successfully, but these errors were encountered: