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

[Cyberduck]

#11542: Unable to locate full error message returned by server
------------------------+-------------------------
 Reporter:  M-Pixel     |         Owner:  dkocher
     Type:  defect      |        Status:  reopened
 Priority:  normal      |     Milestone:  7.8.2
Component:  s3          |       Version:  7.7.2
 Severity:  normal      |    Resolution:
 Keywords:              |  Architecture:  Intel
 Platform:  Windows 10  |
------------------------+-------------------------
Changes (by M-Pixel):

 * status:  closed => reopened
 * resolution:  duplicate =>


Old description:

> 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?

New description:

 I was uploading some files to a self-hosted endpoint, and got an error
 (attached - the specific error is not relevant, but its display is).  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 endpoint that I used, 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?'''

--

Comment:

 This issue is not a duplicate of #11547.  That issue is regarding
 inability to upload a file.  My issue is regarding inability to retrieve
 error information.  I'm removing any mention of the specific error that I
 ran into, to avoid confusion.

 My upload failure was due to a server-side issue that I was able to
 resolve, so, I don't care about the specific error.  I do care (a lot)
 about being able to diagnose errors in general.  My question has not been
 answered, and the linked "duplicate" doesn't answer that question, so I'm
 re-opening this.

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