-
Notifications
You must be signed in to change notification settings - Fork 56
Cannot load test data #42
Comments
I checked load_test_data.sh and found out the problem is within this line
$POSTGRES_NAME uses the database "cp-dojos-development" but when I look into this database it has no tables so of course any INSERT state fails. Where can I find the schema for cp-dojos-development? |
Migrations are ran/checked upon each run, try running ./localdev run zen once before using testdata |
there is no testdata, the database cp-dojos-development is emtpy...! |
The tables are created through migrations scripts which are run when the service is ran (ie : https://github.com/CoderDojo/cp-dojos-service/blob/master/service.js#L39 ) |
without test data there is no german version of the page so i cannot try and fix this issue: CoderDojo/community-platform#856 also, without testdata i cannot login to try and replicate the bug. i can't even register as a new user on localhost since the "Select a user type" dropdown is not populated with the various coderdojo usertypes (Parent/Guardian, Mentor....) i'd really love to fix some issues on the platform but without a working local dev environment i cannot do anything :( |
I'll try to have a look soon, but you don't need the test-data to run zen, running it with empty data is also possible |
but how can i login without the testdata? also: the translation file is several files/folders, not sure what is needed there.... |
I don't believe you need any data to get it running,(as you can still register locally). Like I said, I'll have a look at it asap though. |
Hye, just tested here, testdata works when migrations are ran before, run |
sorry for responding so late :) did a git pull, ran npm install and ./localdev run zen and now the data migration worked...! |
well actually.....cheered too early. I was trying to login once using [email protected] / test but then all just fell apart. when i execute ./localdev run zen i now get a strange error and localhost is not available: Error running service: Error running command: node ./service.js - Error: Command failed: node ./service.js Error: Cannot find module '../build/Debug/addon'
Error: Cannot find module '../build/Debug/addon'
Error: Cannot find module '../build/Debug/addon' 2016-06-28T14:54:30.263Z ewp8fatj3t0a/1467125668925/23347/- INFO client {type:web,port:10303,pin:role:cd-users,cmd:} Error: listen EADDRINUSE 0.0.0.0:10306 Error: listen EADDRINUSE 0.0.0.0:10306
Error: listen EADDRINUSE 0.0.0.0:10306
Error: listen EADDRINUSE 0.0.0.0:10306 events.js:160 Error: ENAMETOOLONG: name too long, stat 'workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests/workspace-zen/cp-e2e-tests' |
did a "npm rebuild" and now get a different error which sums up as this:
did "npm install --save seneca" but this does not help/change anything.....also removed the node_modules folder and ran "npm install" again no success. btw: running node 6.2.2. and npm 3.9.5. |
We didn't test on node 6.2 so far until we have proper tests, so that only 0.10.43 is the recognized version which runs properly |
localhost:8000 is working fine but when I execute
i get lots of postgres-related errors. attached my postgres logfile
postgresql_error_log.txt
The text was updated successfully, but these errors were encountered: