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

feature request : "skip this" option on DL error #5108

cyberduck opened this issue Aug 17, 2010 · 1 comment

feature request : "skip this" option on DL error #5108

cyberduck opened this issue Aug 17, 2010 · 1 comment


Copy link

@cyberduck cyberduck commented Aug 17, 2010

90d53d9 created the issue


This is a bug slash feature request =)

When downloading large websites for archiving purposes, an error can occur that stops the download stream. For example, a file that has changed its name during the course of the transfer, or a file that is deeply nested in the site that cannot be read due to permissions problems. When this happens, Cyberduck stops, providing the error and giving two buttons : cancel or try again.

For me, here's the bug: when I hit try again it restarts the download from the beginning, rather than the point of failure.

Request : the following four buttons would appear : cancel, retry (which would retry at the point of failure), restart transfer (which would restart the transfer from the beginning) and skip, which would ignore the error and just move on to the next file. There would also be a check box marked "skip all future errors" which would do just that, for the transfer in progress.

Thanks and best regards,

Joseph Beeson

Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 18, 2010

@dkocher commented

Thanks for your report. The error report is displayed at the end of the transfer summarizing the errors occured. Choosing Retry should only attempt to transfer the files again that have failed are not yet marked as complete.

If you cannot confirm this behaviour as described, please reopen the ticket.


@cyberduck cyberduck closed this Aug 18, 2010
@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.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants