-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy to 0.4 network #6
Comments
get it all on one v0.3.11 node, then run a migration on it and now its an 0.4.0 node |
Isn't the geoip dag currently used by the webui broken? We'll need scripts to reproduce it from the source geoip data. |
Nope @krl fixed it :) all the data is on the 0.3 network atm |
@dignifiedquire woot! :D |
well looks like I was too excited trying to pull down all the refs fails on the 0.3 network :( |
Okay nothing is working :( no idea why though I did the following Run $ node geoip-gen.js ../GeoLiteCity_20150407/GeoLiteCity-Blocks.csv ../GeoLiteCity_20150407/GeoLiteCity-Location.csv Update the main hash with the return value After that the look ups fail with
and $ ipfs refs -r QmQQ3BUpPjgYiTdhp4H9YWSCtoFXs8t91njhpvXNNLd3yB
Qmdc6WT9mjNbEqgXQZ4vrXKpua3gh1oY3uCDasxmX5DvF6
QmWNYkjWPJ4w3ejg5RHHaefS5bGt3e1DcoFf1BhSiU6P8B
QmTU5PW7ZX86K39FM84rWLSoReA84TDsQ9JDP3sQ29Jywj just hangs :( |
Upon the update of js-ipfs-api to 2.13, I managed to successfully the lookup:
Also, with the js-ipfs-api update, the geoip-gen.js script worked and completed successfully, resulting in the following hash After updating the GEOIP root hash to the new one, it thrown this error:
|
@diasdavid was this on 0.4 (which commit) or on 0.3.11? |
|
@krl we need to put the data onto the 0.4 network, any pointers on how to easiest do this
cc @whyrusleeping @lgierth for ideas
The text was updated successfully, but these errors were encountered: