-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add a team construct #66
Comments
looks like prod is broken. having a look |
not sure but adding three teams into prod then running a migrate seems to have fixed it:
|
Odd. Teams should be optional, and the migrate should happen on every deploy. Robert Loomans On 26 Feb 2016, at 21:31, Mike Villis <[email protected]mailto:[email protected]> wrote: not sure but adding three teams into prod then running a migrate seems to have fixed it: $ heroku run python manage.py migrate --app measuremate — This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities "Suncorp". |
I'm still not sure what's happened. does appear to be enforcing a team for assessments: Here was the error in the deploy (failed silently)
Full Output:
|
apologies.... the reason in fixtures failed was because the migrate failed
looks like form validation fails for assessments because the model does not include I have a feeling that the issue may be because we have the same related_name in the assessment model? I don't understand why there would be a constraint linking template id with team id:
|
I wonder if doing a flush, migrate and loaddata will resolve it. Robert Loomans On 27 Feb 2016, at 17:34, Mike Villis <[email protected]mailto:[email protected]> wrote: apologies.... the reason in fixtures failed was because the migrate failed django.db.utils.IntegrityError: insert or update on table "measure_mate_assessment" violates foreign key constraint "measure_mate_asses_template_id_a871e848_fk_measure_mate_team_id" looks like form validation fails for assessments because the model does not include blank=True. I have a feeling that the issue may be because we have the same related_name in the assessment model? I don't understand why there would be a constraint linking template id with team id: — This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities "Suncorp". |
it's all running again perfectly. btw...I never had an issue locally running the migrate........but i'm not using all the setup data...... i'm guessing when we're serious about prod prod we won't be running the assessment fixture. |
@rloomans are you happy to refactor this one? I can help out just yell! |
@mvillis almost done... just have to clean up the lint complaints |
nice work. Looking great! |
anything left on this one? |
The validation error message is broken. I'll leave editing team details for another card. Robert Loomans
|
#131 created |
Validation is fixed. |
Team --> The bunch of people doing an assessment together - responsible for the assessment.
Maybe this is a group of labels?
The text was updated successfully, but these errors were encountered: