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

Unable to locate full error message returned by server #11542

Closed
cyberduck opened this issue Jan 14, 2021 · 3 comments
Closed

Unable to locate full error message returned by server #11542

cyberduck opened this issue Jan 14, 2021 · 3 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

98de19a created the issue

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


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Actual error duplicate for #11547.

@cyberduck
Copy link
Collaborator Author

98de19a commented

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.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you try to reproduce with the current snapshot build. The fix in 8e3c45f should actually resolve this reporting eventually the original error instead of the application error we had.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants