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.
OH, hah! yeah, this should be a simple case to guard against. just need to reject arguments to dep ensure -add that come back to the same project as we're currently in. i...guess? hmm. it's actually kinda weird we can get here at all.
well, this'll take a little tracing to see how we reach this path, but the fix should be pretty straightforward.
so basically, i think this should just amount to one more check in this loop, comparing the parsed root to the current project's root and failing out if they're the same.
we'll want to add another harness test to capture this specifically, too. there's a README on how to write those in general, and then lots of examples to work from. though this case may be a bit tricky, as i can't recall what the root of the project in the harness tests actually ends up being - we might have it hardcoded to github.com/golang/notexist.
What version of
dep
are you using (dep version
)?1963157
What
dep
command did you run?I have a library (
github.com/F21/some-lib
) in my GOPATH. I then accidentally ran dep inside the project importing itself.What did you expect to see?
Maybe there should be a nicer error message rather than a panic?
What did you see instead?
There was a panic
The text was updated successfully, but these errors were encountered: