yadayada
commented
7 years ago There seems to be logic in place to resume uploads when the connection interrupts but this does not work for interrupting the upload (i.e. SIGKIILL).
I have not investigated in which cases files are lost or appear as partial uploads. There is no client-side logic involved that controls the behavior.
Resumable uploads were announced by Amazon (last year?), but I think that feature has not been implemented.
Incomplete file downloads will be resumed automatically. Aborted file uploads are not resumable at the moment.
Does this mean that there is a special logic involved in the exit trap that will clear the interim state? Could we add an option to acd_cli upload to skip this? e.g. acd_cli upload --resumeable?
I see no good reason for changing the interrupt handling to prematurely and cleanly end uploads since there is no possibility to resume them later.
philipp-spiess
How would one resume an aborted upload? There seems to be logic in place to resume uploads when the connection interrupts but this does not work for interrupting the upload (i.e. SIGKIILL).
I'm building a scheduled uploader that runs 8hrs/day to keep my home internet snappy during the day and I have a file that takes more than 8hours to download. I'd like to abort the upload and continue it on the next day.
Based on the documentation website:
Does this mean that there is a special logic involved in the exit trap that will clear the interim state? Could we add an option to
acd_cli uploadto skip this? e.g.acd_cli upload --resumeable?