tigerang22

@fgregg thanks for the response. Based on previous comments from @f-hafner, I switched from 2.0.17 back to version 2.0.11, with my own fix to the KeyError issue, the training seems...

Let me do some testing and will let you know...

@fgregg It looks that version 2.0.14 introduced the issue, while 2.0.13 is still ok despite the KeyError problem. @f-hafner can you please try your link use case using 2.0.13 and...

@fgregg any insight on the issue and when a future release would have the fix? Thanks

@fgregg great! I will give it a try shortly.

@fgregg I encountered a KeyError related to the datetime field type and it turns out that your commit yesterday doesn't have variables/date_time.py anymore. Are we expected to add that as...

@fgregg I solved the datetime type issue by resetting my virtual environment. Just completed test of commit aa2b04e against my previous dataset. The same problem unfortunately still exists for me,...

> @fgregg Great! I will give 2.0.23 a shot.

@fgregg I have just tested 2.0.23 and unfortunately the same issue exists. Are there any fine tuning options that might be affecting this, such as calling deduper.prepare_training(temp_d) with dynamic sample_size...