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

Resume not possible after local file not found #7791

Closed
cyberduck opened this issue Feb 13, 2014 · 3 comments
Closed

Resume not possible after local file not found #7791

cyberduck opened this issue Feb 13, 2014 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 13, 2014

afd8915 created the issue

I had stopped an upload of a large file from an external drive to S3. I clicked resume without realising my external drive was unmounted. Cyberduck predictably showed an error message. It unpredictably marked the file as 0 bytes with status upload complete. The status should have been left as is on an error, allowing me to mount the drive and resume.

This obviously applies to whatever other addressable errors could cause a resume to fail, the mounting issue just happens to be what caused it for me.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 13, 2014

@dkocher commented

In 46d61d0.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 4, 2014

@dkocher commented

Reverted in 334a4a7.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 4, 2014

@dkocher commented

New fix in 2e29a6a.

@cyberduck cyberduck closed this Jun 4, 2014
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants