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
Hangs when click on a unfinished upload file left after failure to complete upload into encrypted folder #10759
Comments
Thanks for your detailed bug report. I tried to reproduce this issue with selecting an unfinished upload to Wasabi S3 into a Cryptomator vault but cannot reproduce the crash by selecting the file. |
I can however reproduce a crash when opening the Info panel. |
Well, when this happens, the hidden file is listed more than once - in the bucket root, and in each folder along the path to the folder into which the file is being uploaded. In the attached screen shot (HiddenFileEntries.jpg), you can see 2 files whose upload failed. The target directory to which the files were being uploaded is Blaise-Backup/Magni/Diff. You can see an entry for each failed upload in each folder: Blaise-Backup (bucket root), Magni, and Diff. If I delete the entry in the bucket root, the other 2 entries remain in the sub-folders (Magni and Diff). If I click Refresh, these "ghost" entries are removed. But if I click on any of the remaining entries (e.g., right-click, intending to delete), Cyberduck locks up, as described. I have waited as long as 30 minutes to see if it comes back, but it doesn't - I have to kill the Cyberduck process. I hope that helps ... |
Ticket retargeted after milestone closed |
Sorry for not following up on this earlier. Can you still reproduce this in the current release? |
I tried to reproduce by interrupting an upload into a Cryptomator vault using Cyberduck CLI with |
Milestone renamed |
A file upload via Duck CLI to a Cryptomator vault failed. The last 8 lines of Duck output follow:
Here is the duck command issued:
The target folder ("Server") is a cryptomator vault. This happens occasionally, and when it does, a "hidden" file is left behind, as seen in attached screen shot. (long file name, "TKVFDLZCW ..."). I issued the same Duck command again, and the upload succeeded. But the hidden file remains, so I'm guessing that the second successful upload did not "resume" from the first failed upload. This seems common (doesn't resume) and maybe happens because the target folder is a Crytomator vault.
After the second successful upload, I opened Cyberduck, and when I click on the hidden file (to delete it), Cyberduck hangs. You can't click on anything - the window does not respond to any input, nor does the window title bar display "not responding". I fact, it won't even get focus.
When I kill the process (by clicking on the close box of the task bar button), a message box is displayed for a fraction of a second just before the window is closed. It's too quick to read the message.
This occurs reproducibly on Windows 10 running Cyberduck 7.01. When I run Cyberduck 6.9.4 on a Windows 8.1 box, it does not hang.
Let me know if I can provide you with any other information.
Attachments
Hang-v7.01.jpg
(244.0 KiB)HiddenFileEntries.jpg
(191.1 KiB)The text was updated successfully, but these errors were encountered: