I"m running some longer (several hours) calculations (spikesorting) in the make of a table, occasionally I get LostConnectionError: Connection was lost during a transaction, although everything ran correctly. Before I also get [WARNING]: MySQL server has gone away. Reconnecting to the server.
In the make I have only a single insert call. I assume the transaction is started when call to make is made? Solution at the moment is to call populate again and load the processed files instead of generating them.
Reproducibility
Linux 6.5.0-45-generic #45~22.04.1-Ubuntu
Python 3.10
datajoint 0.14.3
Difficult to reliably reproduce as it doesn't always occur and seem to depend on a re connection happening during make call.
Expected Behavior
Make should handle long calculations and potential re connection during this time.
Bug Report
Description
I"m running some longer (several hours) calculations (spikesorting) in the make of a table, occasionally I get LostConnectionError: Connection was lost during a transaction, although everything ran correctly. Before I also get [WARNING]: MySQL server has gone away. Reconnecting to the server.
In the make I have only a single insert call. I assume the transaction is started when call to make is made? Solution at the moment is to call populate again and load the processed files instead of generating them.
Reproducibility
Difficult to reliably reproduce as it doesn't always occur and seem to depend on a re connection happening during make call.
Expected Behavior
Make should handle long calculations and potential re connection during this time.
Additional Research and Context
not sure if this is related issue https://github.com/datajoint/datajoint-python/issues/896
Best, Artur