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

Uploaded files changed to zero length upon completion #1149

Closed
cyberduck opened this issue Jun 29, 2007 · 2 comments
Closed

Uploaded files changed to zero length upon completion #1149

cyberduck opened this issue Jun 29, 2007 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 29, 2007

6d83706 created the issue

This is a repeatable bug.

-(Uploading to a MediaTemple gridserver host (Pure-FTPd))*

Larger files complete upload, and then an Operation Timed Out dialog is presented ("cancel" and "try again" buttons)
Both buttons result in the file being reduced to zero length.


-Notes:*

I have confirmed that the file is successfully being uploaded each time, if I ssh in (or connect using another ftp client) while the error dialog is on screen, I can rename the file and it will stay intact.

If I copy the file, I will have the original reduced to zero length, and my copy will be intact (obviously)

Attempted courses of action:

  • made sure that Preferences : Transfers : Uploads : Duplicate Files was set to "Try to resume"
  • unchecked Preferences : Transfers : Permissions : Uploads : Change Permissions (in case a separate thread was timing out and causing the whole operation to be considered failed)
  • Preferences : Advanced : Send NOOP is confirmed on

Actions I have not attempted:

  • Uncheck Preferences : Transfers : Timestamps : Preserve Modification Date

Like I said, this is repeatable - as I've done it for about a dozen uploads, trying different combinations - only had the time to register for ticket submission now.

The first time it happened was after uploading a 900mb archive at 35kb/s on a time-critical project.
As much as this was a problem, I'm at least tech savvy enough to have a workaround - but others may not, hence the high priority on this ticket.


This bug only occurs with large files.

I hypothesize that the primary connection thread (browser) may be hitting the 15 minute timeout, and some flag is affecting the transfer threads too.

Since the "send NO OP" option is set, I wouldn't imagine this being the case, but without reviewing source I can only guess.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 9, 2007

@dkocher commented

Can you replicate the problem in a recent 2.8 build available (http://update.cyberduck.ch/nightly/)?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 12, 2007

@dkocher commented

Cannot replicate this in 2.8.

Loading

@cyberduck cyberduck closed this Jul 12, 2007
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants