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 Aug 31, 2021. It is now read-only.
Based on golang/dep#433 it seems that dep is not able to handle case insensitivity, specifically with github. This is causing some weird behavior in VDB, like adding VulcanizeDB into it's own vendor directory.
Steps to reproduce:
clone the project
cd into the VulcanizeDB directory that was created
run dep ensure
notice that "github.com/vulcanize/vulcanizedb" is added to Gopkg.lock as a dependency
if you make a change to your local VulcanizeDB project (i.e. add an extra print statement to the sync command) and then rebuild, the change you've made will not be reflected. I think that this is because the binary that is created is using the "vendored vulcanize db" instead
A quick fix is to locally change the VulcanizeDB directory to vulcanizedb (no capitals), but we should instead figure out a better way to handle this - perhaps changing the repo name would help, but maybe there is another solution.
The text was updated successfully, but these errors were encountered:
elizabethengelman
changed the title
Update vulcanize to properly handle dep not handling case insensitivity with github repos
Update vulcanize to properly handle dep's issue with case insensitivity (for github repos)
Jun 12, 2018
Based on golang/dep#433 it seems that dep is not able to handle case insensitivity, specifically with github. This is causing some weird behavior in VDB, like adding VulcanizeDB into it's own vendor directory.
Steps to reproduce:
VulcanizeDB
directory that was createddep ensure
Gopkg.lock
as a dependencysync
command) and then rebuild, the change you've made will not be reflected. I think that this is because the binary that is created is using the "vendored vulcanize db" insteadA quick fix is to locally change the
VulcanizeDB
directory tovulcanizedb
(no capitals), but we should instead figure out a better way to handle this - perhaps changing the repo name would help, but maybe there is another solution.The text was updated successfully, but these errors were encountered: