Hello,
recently whenever I'm running 'manage.py run_ptop --all' I see a lot of
errors similar to this one:
2014-03-24 13:43:06,256 INFO listener
(pillowtop_corehq.pillows.formdata.FormDataPillow.lech-pc) setting
checkpoint: 110262
2014-03-24 13:43:06,962 INFO bad update in form listener for line: { ...
, 'problem': u'Form is a duplicate of another! ( ... )', '_id': ' ... ',
'history': []}
Instance had doc id ( ... ) different from meta instanceID ( ... )!
Is there anything I need to change in the m4change reports to make this
error go away, or is this an issue somewhere in the main code?
Furthermore, do the errors even matter where our reports are concerned, or
can I just ignore them altogether?
Regards
Lech
Hi Lech
The errors won't affect your reports so you can ignore them. The was also a
fix that was merged into the CommCare HQ main codebase this morning so if
you update your code you shouldn't get that error any longer.
Another thing that you may find useful is that you do a fast re-index of a
single fluff pillow as follows:
./manage.py
ptop_fast_reindex_fluff
custom.m4change.models.McctMonthlyAggregateFormFluffPillow
If you want to run them continuously you can also do this on a per-pillow
basis with:
./manage.py
run_ptop --pillow-name=custom.m4change.models.McctMonthlyAggregateFormFluffPillow
···
On 24 March 2014 15:52, Lech Różański wrote:
Hello,
recently whenever I'm running 'manage.py run_ptop --all' I see a lot of
errors similar to this one:
2014-03-24 13:43:06,256 INFO listener
(pillowtop_corehq.pillows.formdata.FormDataPillow.lech-pc) setting
checkpoint: 110262
2014-03-24 13:43:06,962 INFO bad update in form listener for line: { ...
, 'problem': u'Form is a duplicate of another! ( ... )', '_id': ' ... ',
'history': []}
Instance had doc id ( ... ) different from meta instanceID ( ... )!
Is there anything I need to change in the m4change reports to make this
error go away, or is this an issue somewhere in the main code?
Furthermore, do the errors even matter where our reports are concerned, or
can I just ignore them altogether?
Regards
Lech
--
You received this message because you are subscribed to the Google Groups
"CommCare Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Simon Kelly
Senior Engineer | Dimagi South Africa