[Cyberduck-trac] [Cyberduck] #10759: Cyberduck hangs when click on a "hidden" file left after failure to complete upload into cryptomator folder

[Cyberduck]

#10759: Cyberduck hangs when click on a "hidden" file left after failure to
complete upload into cryptomator folder
----------------------------+------------------------
    Reporter:  MarkBlaise   |      Owner:
        Type:  defect       |     Status:  new
    Priority:  normal       |  Milestone:
   Component:  cryptomator  |    Version:  7.0.1
    Severity:  normal       |   Keywords:
Architecture:  Intel        |   Platform:  Windows 10
----------------------------+------------------------
 A file upload via Duck CLI to a Cryptomator vault failed. The last 8 lines
 of Duck output follow:

 {{{
 [▮▮▮▮▮▮▮▮▮▮▮▮▮                 ] 350.0 MiB (367,001,600 bytes) of 799.0
 MiB (43%, 7.9 MB/sec, 60 seconds remaining)
 [▮▮▮▮▮▮▮▮▮▮▮▮▮                 ] 340.0 MiB (356,515,840 bytes) of 799.0
 MiB (42%, 7.6 MB/sec, 64 seconds remaining)
 Transfer incomplete…
 Upload
 TKVFDLZCWLMMFWR4QANKZW6PIXSYIAOTLGEKRGVB5H4RZJJFXUB4BFVCJYL2XR4VMJ4K3LGSH4MA====
 failed. We encountered an internal error.  Please retry the operation
 again later. Please contact your web hosting service provider for
 assistance.


 [▮▮▮▮▮▮▮▮▮▮                    ] 280.0 MiB of 799.0 MiB
 [▮▮▮▮▮▮▮▮▮▮                    ] 270.0 MiB of 799

 }}}

 Here is the duck command issued:

 {{{
 duck  -P --existing resume --parallel 32     --upload
 wasabisys://T5ZHIOV9VGMNBAKU1HQ4@Blaise-Backup/Server/ \\Odin\Backup-
 Staging\Server\20190710-031246-D_B2D000217.bkf

 }}}

 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.

--
Ticket URL: <https://trac.cyberduck.io/ticket/10759>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows