open-city / recycling

Crowdsourcing data about which residential buildings do not have recycling in Chicago
MIT License
27 stars 24 forks source link

Migration issue when running npm install #151

Closed austynguo closed 8 years ago

austynguo commented 8 years ago

Hi guys, awesome project. I'm a bit new to this so please bear with me and apologies in advance.

I'm trying to set up a fork of this on my machine and have followed the setup instructions on Wiki and readme. I'm running into an issue when running npm install: Fatal error: Can't extract geo keys from object, malformed geometry?. I am also unable to run a local server on localhost:3000 using node server.js (no terminal output can be seen, though there is no app hang). Not sure if this is related to the first issue.

I'm running nodejs v4.4.3, npm v2.15.1 on Debian 8. I've tried deleting the dependencies in /node_modules/ and running npm install to repopulate the modules but that hasn't done anything noticeable.

Any help would be greatly appreciated and let me know if I can help with any other info.

See install/error log:

aguo@debian:~/Dropbox/University of Sydney/2016/bikewebapp$ npm install
npm WARN deprecated lodash@0.9.2: Grunt needs your help! See https://github.com/gruntjs/grunt/issues/1403.
npm WARN deprecated graceful-fs@1.2.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@2.0.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
-
> fibers@1.0.10 install /home/aguo/Dropbox/University of Sydney/2016/bikewebapp/node_modules/grunt-mongo-migrations/node_modules/fibrous/node_modules/fibers
> node build.js || nodejs build.js

`linux-x64-v8-4.5` exists; testing
Binary is fine; exiting
-
> recycling-server@0.0.1 postinstall /home/aguo/Dropbox/University of Sydney/2016/bikewebapp
> script/postinstall.sh

Running "migrate:all" task
>> Running migration `20150130233457984_add_ward_info`
Fatal error: Can't extract geo keys from object, malformed geometry?:{ coordinates: [ [ [ [ -87.68562300000001, 41.939485 ], [ -87.685579, 41.937666 ], [ -87.683109, 41.935872 ], [ -87.678237, 41.93593 ], [ -87.67813099999999, 41.931877 ], [ -87.67832300000001, 41.930401 ], [ -87.6781, 41.928085 ], [ -87.679705, 41.928464 ], [ -87.68276299999999, 41.925879 ], [ -87.682738, 41.924969 ], [ -87.687642, 41.924901 ], [ -87.68741, 41.917568 ], [ -87.686919, 41.917574 ], [ -87.684909, 41.916216 ], [ -87.684952, 41.915228 ], [ -87.68241999999999, 41.913582 ], [ -87.68214, 41.903107 ], [ -87.68458, 41.903061 ], [ -87.68451, 41.900331 ], [ -87.68696, 41.900293 ], [ -87.686843, 41.895743 ], [ -87.684397, 41.895785 ], [ -87.684371, 41.894871 ], [ -87.68192500000001, 41.894918 ], [ -87.681949, 41.895827 ], [ -87.675832, 41.895932 ], [ -87.675884, 41.897752 ], [ -87.67344, 41.897787 ], [ -87.673489, 41.899614 ], [ -87.677156, 41.899551 ], [ -87.67722999999999, 41.902256 ], [ -87.67967400000001, 41.902217 ], [ -87.679907, 41.91044 ], [ -87.670134, 41.910597 ], [ -87.670231, 41.914292 ], [ -87.667233, 41.914298 ], [ -87.66497699999999, 41.910668 ], [ -87.665656, 41.910658 ], [ -87.665243, 41.910001 ], [ -87.66520199999999, 41.908844 ], [ -87.664002, 41.908761 ], [ -87.663883, 41.905192 ], [ -87.66267000000001, 41.905209 ], [ -87.662621, 41.903723 ], [ -87.662628, 41.903409 ], [ -87.666484, 41.903359 ], [ -87.663732, 41.901588 ], [ -87.667444, 41.901524 ], [ -87.667367, 41.898798 ], [ -87.66492, 41.89884 ], [ -87.664905, 41.896111 ], [ -87.667292, 41.896074 ], [ -87.667185, 41.892427 ], [ -87.67450599999999, 41.892309 ], [ -87.674486, 41.891585 ], [ -87.676929, 41.891548 ], [ -87.676974, 41.893173 ], [ -87.686763, 41.89302 ], [ -87.68678800000001, 41.893928 ], [ -87.689243, 41.89391 ], [ -87.689307, 41.895716 ], [ -87.691773, 41.895702 ], [ -87.691818, 41.897513 ], [ -87.689351, 41.897535 ], [ -87.689396, 41.899354 ], [ -87.696791, 41.899283 ], [ -87.696856, 41.901994 ], [ -87.69193199999999, 41.902041 ], [ -87.691908, 41.901151 ], [ -87.68944399999999, 41.901176 ], [ -87.689465, 41.902063 ], [ -87.687006, 41.902087 ], [ -87.68702, 41.902767 ], [ -87.687123, 41.906667 ], [ -87.688355, 41.906656 ], [ -87.688402, 41.90848 ], [ -87.68962999999999, 41.908467 ], [ -87.689667, 41.910294 ], [ -87.69908, 41.910198 ], [ -87.69919299999999, 41.913941 ], [ -87.697097, 41.914004 ], [ -87.697464, 41.92663 ], [ -87.687709, 41.926716 ], [ -87.687743, 41.927786 ], [ -87.692914, 41.930549 ], [ -87.697648, 41.933339 ], [ -87.697823, 41.939393 ], [ -87.687911, 41.93946 ], [ -87.687939, 41.940366 ], [ -87.685647, 41.940395 ], [ -87.68562300000001, 41.939485 ] ] ] ], type: "MultiPolygon" }
Cache flushed
{ 'localhost:11211': true }
austynguo commented 8 years ago

Ok, so I set this up in a Ubuntu VM instead using the same steps, same versions of nodejs and npm and got past the migration stage. Running into an issue with node server.js or npm start not creating a listener on port 3000 unless I comment out the if statement leaving only the else statement contents. Closing the issue for now

alexkahn commented 8 years ago

Awesome! Feel free to file issues if you run into any trouble!