-
Notifications
You must be signed in to change notification settings - Fork 1k
dep: Panic observed on init #1130
Comments
Can you provide the original glide config files? Looks like a bug in the glide importer, notice that all the initial locks are the same revision |
Hey @carolynvs for sure, please see below. glide.yaml
glide.lock
|
@carolynvs when we get to the fix on this one, can we try to make sure to include some regression tests for this + similar cases? |
Ah okay yeah I totally did not expect that a valid glide.lock would contain empty revisions - name: github.com/garyburd/redigo
version: "" I'll make sure #1100 has a testcase for this as well so that it's covered for all importers. |
@simar7 FYI, I am only looking at fixing how dep handles missing revisions in glide.lock. I'm not sure if the glide files you posted are "scrubbed"(?) but the lock is invalid. Even after I fix the panic, |
@carolynvs Correct me if I'm wrong but I believe the reason |
I just ran |
The panic has been fixed in #1100. |
Hey folks,
Just noticed dep panic out while I was trying to
dep init
a repo that was previously managed with glide.What version of
dep
are you using (dep version
)?v0.3.0-248-gd3e738d
What
dep
command did you run?What did you expect to see?
dep init working without a panic and setting up dependencies as expected.
What did you see instead?
dep panicking.
The text was updated successfully, but these errors were encountered: