I’ve installed the new 1.3 prodigy (linux) to use the new ner.make-gold recipe and every time the recipe saves annotation in the database (either manually or when the batch is full) i get a Segmentation Fault and the server stops. I tried it with several recipes (ner.manual, ner.make-gold, ner.teach) and several database (default SQLITE and own amazon rds psql db) and the segmentation fault always occure.
I downgraded to 1.2 and everything seems to work just fine.
The new 1.3 version seems to have a little bug on the saving part.
Thanks for the report – that’s very strange! So just to be clear: is the segfault happening with the ner.make-gold recipe? That recipe doesn’t use an update callback, so I’m puzzled as to what could be going on here.
Thanks for the report – this is indeed very strange. Did the traceback provide more details on where the segfault occurred, or could you run it again with PRODIGY_LOGGING=basic and post the last entries in the log?
Also, here’s the standalone, bare-bones version of what happens internally when you save a batch of answers (e.g. by making a request to /give_answers). Does the script below also cause the error for you?
I don’t suppose you could share the examples you’re working with?
The error is likely to be occurring within spaCy, not Prodigy. Even in the ner.manual recipe, we still pass the text to spaCy to tokenize it.
Is it possible that you have an example with extremely long text? Empty text fields shouldn’t crash it, but that’s another possibility that comes to mind.
Ok I just found out the error. I was working on a docker image using a light-weight python image python:3.6.2-alpine. I updated my image using a more complete environment (python:3.6.4-stretch). The issue must have been the C libraries that the light-weight image was using that doesn’t work anymore on the 1.3 version of Prodigy.
Thank you for your time and sorry for the inconvenience.