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

Unclear "Transfer incomplete" notification on successful (?) upload after reconnect #16449

Open
lostminds opened this issue Oct 24, 2024 · 0 comments

Comments

@lostminds
Copy link

Describe the bug
Some times when being idle for a while the connection to a server will be lost, causing Cyberduck to first reconnect when you try to transfer a file. This is normal and expected. However, there seems to be a bug that if you edit a file that will be re-uploaded on save this upload is reported as "Transfer incomplete" even if it did complete if the Cyberduck was succussful only after retrying.

To Reproduce
Steps to reproduce the behavior:

  1. Sign in to a server click to "edit" a text file.
  2. Stay idle until the connection is dropped (not sure why or for what servers this happens, but it does)
  3. Make a change to the local file and save it to trigger the re-upload in Cyberduck
  4. Observer Cyberduck initially failing since the connection has dropped, then reconnecting and successfully (?) uploading the edited file
  5. Get "Transfer incomplete" notification even though the transfer was successful, making you think the transfer failed so you need to re-upload it to be sure.

Expected behavior
Best case would be that the connection was kept alive and not dropped. But this may be beyond the capability of Cyberduck depending on the server. If it is dropped, the connection should be reinitiated as it appears it is, and in this case if the upload is then successful it should report "Transfer complete" instead of "Transfer incomplete"

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: 15.0.1
  • Version 9.0.2 (42108)

Log Files
Please include the log file. You can reach the logging output in Preferences → Connection.
cyberduck(trimmed).log

Taking a look in the log there are a lot of repeated error/warning messages that don't seem to be related to this issue causing the log file sizes to bloat (83MB) so I cut out the log for the last hour or so when the issue above appeared above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@lostminds and others