You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
Our CI started failing out of the blue, and we were able to reproduce the same problem locally on a Mac after doing a: go get -u github.com/golang/dep/cmd/dep.
yeah, sorry, this was a bug in #1912 - didn't set loggers correctly when -v wasn't passed, and the tests missed it because they all override the logger in a way that masks the problem. It should be fixed now.
Note, though, that your CI may have a bumpy ride unless everyone else is also running the very latest of dep - #1912 also made significant changes to the way Gopkg.lock is structured. i'm aiming for an official release in the next couple days, but until then, you may want to use a released version instead of tip.
What version of
dep
are you using (dep version
)?installed via go get: v0.4.1-246-g5a7960a4
What
dep
command did you run?Our CI started failing out of the blue, and we were able to reproduce the same problem locally on a Mac after doing a:
go get -u github.com/golang/dep/cmd/dep
.dep ensure
fails with the following error:dep ensure -v
output:What did you expect to see?
It is really strange that -v makes a difference.
What did you see instead?
dep ensure should work like before.
The text was updated successfully, but these errors were encountered: