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

Incomplete upload due to connection factory shutdown prior stream closed #7535

Closed
cyberduck opened this issue Oct 31, 2013 · 6 comments
Closed
Assignees
Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

c304b41 created the issue

I have two computers using Cyberduck. One I have updated to the latest version of Cyberduck and the other is still on the previous version. I can establish connection through S3 on both versions however the new version will only allow one picture to upload before I receive a Transmission incomplete message. I've tried many different folders of images with the same result.
The earlier version is continuing to work perfectly and I don't want to update that computer due to the latest versions issue.
Can you help?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you please post the transcript from the log drawer (⌘-L) of the Transfers window.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This could be related to a fix in cd3dfbc. Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

c304b41 commented

This hasn't changed anything at my end. Can someone explain this issue and fix to me please. Thanks

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 Jeff Darmanin]:

This hasn't changed anything at my end. Can someone explain this issue and fix to me please. Thanks

Can you please post the transcript from the log drawer (⌘-L) of the Transfers window.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed in d70fb9e.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#7610 closed as duplicate.

@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 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants