Open stupidloud opened 2 weeks ago
Hi,
thank you for the bug report. This is not supposed to happen. Have you deleted the unfinished large file as the CLI was uploading the affected file?
I updated the command b2v4 from 4.1 to 4.2, now I cannot reproduce this issue. but a new file version was still added while --incremental-mode is used. the procedure:
This bug is still there. After uploaded a few files, each upload command (same arguments but different files) produced the same error. It's not second upload attempt. Each fresh upload had this error.
Hey,
I'm slightly confused. Is the problem that you are getting an "authorization error", or that the upload session is not continued from where it left off? Or maybe it's both?
I am getting an "authorization error", but not always. I wrote a script to watch a directory, to upload files which were put into. After a few files were successfully uploaded, the upload command continuously reported this error message. To identify the reason, I logined to the b2 web console, confirmed that there is no unfinished parts of those files which referenced.
I think the error is related to your server. And I think you should continuously upload a few files to reproduce this error.
To resolve, I remove --incremental-mode from the command line.
sometimes my bucket has unfinished uploading large files, I always manually deleted them. I assume
--incremental-mode
has a capability to append data to the these files, instead of adding another version. but the uploading is failed with the message on the first line.