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

Listing bucket containing multipart uploads fails with error in ListMultipartUploadsResultHandler #9686

Closed
cyberduck opened this issue Sep 11, 2016 · 9 comments
Labels
bug fixed high priority s3
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 11, 2016

a304470 created the issue

When trying to open a bucket containing multipart uploads I get:

Upload some-bucket failed.

Failed to parse XML document with handler class org.jets3t.impl.rest.XmlResponsesSaxParser $ListMultipartUploadsResultHandler.

Note: I'm not trying to upload anything.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2016

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2016

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 17, 2016

@dkocher commented

We cannot reproduce this failure in tests. Do you have a bucket that is accessible for us so we can reproduce the failure?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 19, 2016

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 20, 2016

a304470 commented

Replying to [comment:4 dkocher]:

We cannot reproduce this failure in tests. Do you have a bucket that is accessible for us so we can reproduce the failure?

I may be able to if I'm allowed to send you the permissions via PM or other private means. Would that be possible from your side?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 21, 2016

@dkocher commented

Replying to [comment:6 blacktrash]:

Replying to [comment:4 dkocher]:

We cannot reproduce this failure in tests. Do you have a bucket that is accessible for us so we can reproduce the failure?

I may be able to if I'm allowed to send you the permissions via PM or other private means. Would that be possible from your side?
Definitely. Please create an access token for an IAM user that you can revoke after testing. You can send the credentials to [support@cyberduck.io].

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 21, 2016

@dkocher commented

Ignore XML parsing failures for invalid content from S3 in f72d532.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 22, 2016

a304470 commented

Replying to [comment:9 dkocher]:

Ignore XML parsing failures for invalid content from S3 in f72d532.

Confirming fix. Thanks a bunch!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 11, 2017

@dkocher commented

Milestone renamed

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

No branches or pull requests

1 participant