Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uploads to vault on B2 fail with Sha1 did not match data received #9895

Closed
cyberduck opened this issue Mar 23, 2017 · 7 comments
Closed

Uploads to vault on B2 fail with Sha1 did not match data received #9895

cyberduck opened this issue Mar 23, 2017 · 7 comments
Assignees
Labels
bug cryptomator Cryptomator Vault thirdparty Issue caused by third party
Milestone

Comments

@cyberduck
Copy link
Collaborator

6829145 created the issue

I have created an encrypted vault on B2 using the latest nightly build. All uploads fail with the error message: Sha1 did not match data received.

Screen Shot 2018-03-02 at 7.38.27 pm.png, 400

Uploading the same files to a regular vault works fine.

Thanks for looking into this!


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 0fe452c.

@cyberduck
Copy link
Collaborator Author

f98c03f commented

Just ran into this then:
https://www.dropbox.com/s/6yiqba8xvpiywgg/Screen%20Shot%202018-03-02%20at%207.38.27%20pm.png?dl=0

Running CyberDuck Version 6.4.3 (27644) on MacOS 10.13.3 (17D102)

How shall we debug?

@cyberduck
Copy link
Collaborator Author

f98c03f commented

I've got the dialog still open. I am not sure what "Continue" and "Always" mean here.

Intuitively I am after a "Retry" button to try again, or a "Cleanup" button to remove the corrupted file for a later try.

Is there a log file written anywhere that I can include in this issue? Thanks!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I cannot reproduce the issue with a 346.8MB upload. Can you try again and see if you get the same error again? Possibly there was indeed an issue with saving the file in B2 causing a checksum failure.

@cyberduck
Copy link
Collaborator Author

f98c03f commented

Yeah, it's happened one out of two times that I've tried since the "transfer incomplete" fixes landed. The first was about 10gb and worked fine, this one was about 6gb and had this. Both uploads were many different files.

So happy to have this as not cyberduck's issue. However, I am unsure how to proceed when I get this dialog, or a transfer incomplete notification (which still happens sometimes). In this case, what does "continue" or "cancel" even mean? Does "cancel" do any cleanup? Does "continue" reupload the failed part, or just skip it? Naturally - I want either the failed area to be retried or clean up, so that the entire transfer can complete successfully - continue just seems to imply skip, which would "corrupt" my transfer as data is missing or invalid.

Advice on how to proceed when these things occur would be great, as right now there is no meaningful logs or dialogs to know. Perhaps the suggestion in my earlier comment would be helpful: https://trac.cyberduck.io/ticket/9895#comment:11

Thank you!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:12 dkocher]:

I cannot reproduce the issue with a 346.8MB upload. Can you try again and see if you get the same error again? Possibly there was indeed an issue with saving the file in B2 causing a checksum failure.

If you have set in Preferences → Connection → Repeat failed networking tasks to automatically retry errors, the file transfer has been retried already. The prompt only allows you to continue transferring the remaining files or cancel the transfer.

@cyberduck
Copy link
Collaborator Author

f98c03f commented

So does cancel delete the corrupted files?

Why would I want to continue without all the data passing?

Is it possible to submit a feature request for my suggestions to that dialog?

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug cryptomator Cryptomator Vault thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants