pyinotify automatically notifies the tablesnap UploadHandler for IN_CREATE events if tablesnap is started with the --auto-add option, which causes all kinds of errors for tablesnap, since it starts copying the files to S3 before they are done being written. This pull request just adds a check that will prevent upload on IN_CREATE events unless that is directly specified via the --listen-events argument.
Let me know if this is the wrong way to fix this or if you see any other issues with this code.
pyinotifyautomatically notifies the tablesnapUploadHandlerforIN_CREATEevents if tablesnap is started with the--auto-addoption, which causes all kinds of errors for tablesnap, since it starts copying the files to S3 before they are done being written. This pull request just adds a check that will prevent upload onIN_CREATEevents unless that is directly specified via the--listen-eventsargument.Let me know if this is the wrong way to fix this or if you see any other issues with this code.
This closes #91