Closed B-Hartmann closed 1 year ago
Yes, this makes total sense. Servers also have to reboot at times (overnight, which is when DCOR uploads are running as well), so this problem will haunt us indefinitely.
FYI If you are executing dcor-aid CLI via an external script/program, then DCOR-Aid will return a non-zero exit code if the upload fails. You can use this information to keep track of all failed uploads and e.g. show that list to the user.
@B-Hartmann
Windows 10 Python 3.10.8 dcoraid 0.11.9
I used a custom Python script that makes use of the dcoraid cli to upload data to a DCOR instance. It seems that the connection to the server was interrupted shortly, causing dcoraid to throw an error. It didn't finish the upload job, but my script went on to the next file, which was successfully uploaded. So in this situation, I ended up with a draft dataset on DCOR and a not finished job in the cli, which can be problematic if you don't check the full output of the cmd window again when the process finished. It's easy to overlook issues like that and then you lack some data.
Since it is common (at least for private house holds, at least in Germany) that the internet connection is interrupted shortly every day because the internet service providers assign new ip addresses (IPv4 address shortage), would it make sense to set the process to sleep for 30 seconds in case a "TimeoutError" occurs and then retry to upload or something like that?