Can't start task with current seed data
chiaracoetzee opened this issue · comments
With the current seed data I can't seem to reach the first page of the task. Steps:
- Start server and browse to http://localhost:3000/
- Enter name, select only Condition and Activity
- Click Submit. Welcome page appears.
- Click Start. Returns to http://localhost:3000/
This is blocking my current work item to reproduce the existing MOOCchat workflow from CSCW Experiment 2 R3 in the new system. I'm investigating it. I didn't immediately see any hints on the debug output with "rails server --debug".
Armando said this works in his integration tests so it's likely that I'm populating the seed data incorrectly somehow.
I'll be in soda in about 20m and can check it out with you.
Sent from my iPhone; forgive my terseness
El Jun 23, 2014, a las 12:41 PM, dcoetzee notifications@github.com escribió:
With the current seed data I can't seem to reach the first page of the task. Steps:
Start server and browse to http://localhost:3000/
Enter name, select only Condition and Activity
Click Submit. Welcome page appears.
Click Start. Returns to http://localhost:3000/
This is blocking my current work item to reproduce the existing MOOCchat workflow from CSCW Experiment 2 R3 in the new system. I'm investigating it. I didn't immediately see any hints on the debug output with "rails server --debug".Armando said this works in his integration tests so it's likely that I'm populating the seed data incorrectly somehow.
—
Reply to this email directly or view it on GitHub.
Assigning to Armando after our discussion so he can see if it's his bug. Note that on the current mainline "rake db:seed" seems to fail, to fix this add :questions to attr_accessible in ActivitySchema in app/models/activity_schema.rb
yes, i realized i had accidentally removed attr_accessible :questions, i replaced that adn pushed it.
("accidentally" == removing it did not cause any test to fail, so maybe there should be a regresison for this)
examining the bug this afternoon
Armando Fox
Professor, Computer Science Division
Faculty Advisor, UC Berkeley MOOCLab
fox .at. cs .dot. berkeley .dot. edu
581 Soda Hall MC#1776, Berkeley, CA 94720-1776
+1.510.642.6820 / http://www.cs.berkeley.edu/~fox
TAKE MY CLASS FOR FREE VIA edX: http://saas-class.org
LIKE IT ON FACEBOOK: http://facebook.com/saas-class
TRY MY BOOK (NOT FREE): http://beta.saasbook.info (goes with the course)
On Jun 23, 2014, at 3:16 PM, dcoetzee notifications@github.com wrote:
Assigning to Armando after our discussion so he can see if it's his bug. Note that on the current mainline "rake db:seed" seems to fail, to fix this add :questions to attr_accessible in ActivitySchema in app/models/activity_schema.rb
—
Reply to this email directly or view it on GitHub.
let's use 'issues' to discuss actual isseus (design/arch questions) and let's just use Tracker to assign bugs - you can mark something as a bug rather than a feature.
for derrick's bug, i watched him reproduce it, but in general when you file a bug please describe the procedure to reproduce it. (Section 10.6 in the book :-)
Armando Fox
Professor, Computer Science Division
Faculty Advisor, UC Berkeley MOOCLab
fox .at. cs .dot. berkeley .dot. edu
581 Soda Hall MC#1776, Berkeley, CA 94720-1776
+1.510.642.6820 / http://www.cs.berkeley.edu/~fox
TAKE MY CLASS FOR FREE VIA edX: http://saas-class.org
LIKE IT ON FACEBOOK: http://facebook.com/saas-class
TRY MY BOOK (NOT FREE): http://beta.saasbook.info (goes with the course)
On Jun 23, 2014, at 3:16 PM, dcoetzee notifications@github.com wrote:
Assigning to Armando after our discussion so he can see if it's his bug. Note that on the current mainline "rake db:seed" seems to fail, to fix this add :questions to attr_accessible in ActivitySchema in app/models/activity_schema.rb
—
Reply to this email directly or view it on GitHub.
Note that my Github Issue did in fact include reproduce steps in the first comment. Please let me know if I need to include more information in the future. Using Tracker for bugs is fine - I just didn't know it could be used for that.
no, i can reproduce yours. i found the bug in my code. but i'm having trouble exercising it because something about the chatroom middleware is breaking routing for the regular app.
Armando Fox
Professor, Computer Science Division
Faculty Advisor, UC Berkeley MOOCLab
fox .at. cs .dot. berkeley .dot. edu
581 Soda Hall MC#1776, Berkeley, CA 94720-1776
+1.510.642.6820 / http://www.cs.berkeley.edu/~fox
TAKE MY CLASS FOR FREE VIA edX: http://saas-class.org
LIKE IT ON FACEBOOK: http://facebook.com/saas-class
TRY MY BOOK (NOT FREE): http://beta.saasbook.info (goes with the course)
On Jun 24, 2014, at 10:47 AM, dcoetzee notifications@github.com wrote:
Note that my Github Issue did in fact include reproduce steps in the first comment. Please let me know if I need to include more information in the future. Using Tracker for bugs is fine - I just didn't know it could be used for that.
—
Reply to this email directly or view it on GitHub.