[Cyberduck-trac] [Cyberduck] #11542: Unable to locate full error message returned by server

Cyberduck trac at cyberduck.io
Thu Jan 14 19:42:54 UTC 2021

#11542: Unable to locate full error message returned by server
    Reporter:  M-Pixel  |      Owner:
        Type:  defect   |     Status:  new
    Priority:  normal   |  Milestone:
   Component:  core     |    Version:  7.7.2
    Severity:  normal   |   Keywords:
Architecture:  Intel    |   Platform:  Windows 10
 I was uploading some files to an S3 API, and got an error (see attached).
 The error message was truncated.  The upload continued after I dismissed
 the error message.  After the upload finished, I see "Upload complete" in
 my Transfers window.

 As the administrator of the S3 API that I used (I'm using Cyberduck to
 test out an S3 implementation that I'm evaluating), I should investigate
 the error to make sure that it doesn't indicate an underlying problem that
 ought to be fixed.  In order to do this, perhaps not with this particular
 error, but in general, I may need the full text of the original error, and
 it is useful to have that in a copy-pastable medium (the error message
 window does not allow selecting its text).

 I looked at the Cyberduck log file, but it did not contain a copy of the
 error text.  I searched through Cyberduck's appdata folder, and could not
 find any other log files.  I searched through the GUI, and could not find
 any way to retrieve a copy of the error's original text.  The completed
 transfer has no buttons and no context menu.

 Are errors always lost to the ether?  Is there any way to view non-
 truncated copies?

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

More information about the Cyberduck-trac mailing list