gregglind
commented
9 years ago Type 1:
- 'began' and 'offered' are very very close in timing, and requests can arrive out of order. This works as desinged, and is OK.
- claim: it is still worth pinging on both BEGIN and OFFER for a while,
- until we understand how all the ui really works (i..e, this is a negative test)
- in case we move to a model where began and offer are 'more different'
Type 1: wrong order
151881 packet errors 2015-02-26 10:03:03 {u'updated_ts': u'updated timestamp is same or older than existing data'}
Type 2: Empty POST
151873 packet errors 2015-02-26 09:58:06 {u'question_text': [u'This field is required.'], u'response_version': [u'This field is required.'], u'variation_id': [u'This field is required.'], u'experiment_version': [u'This field is required.'], u'updated_ts': [u'This field is required.'], u'flow_id': [u'This field is required.'], u'person_id': [u'This field is required.'], u'survey_id': [u'This field is required.'], u'question_id': [u'This field is required.']}