Closed mzur closed 5 years ago
I couldn't pin down this issue. There are no error messages and it works fine for many thousands of patches in the tests. Maybe this is an issue with our production database? It might not return all annotations in the same transaction than they were created. This would be strange indeed. I moved the dispatch call out of the transaction to see if it changes anything.
I ran several novelty detection and instance segmentation jobs for testing. This error occurred in none of them (any more). I consider this fixed.
Sometimes the patches for training proposals or annotation candidates are not or only partly generated. There is no error message. Maybe this is an issue of not enough memory again (#26)? This happened for an instance segmentation response with only 219 annotation candidates, though...