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

Jump to bottom

Wrong filesize for upload displayed #5503

Closed
cyberduck opened this issue Dec 4, 2010 · 9 comments
Closed

Wrong filesize for upload displayed #5503

cyberduck opened this issue Dec 4, 2010 · 9 comments
Assignees
@dkocher
Labels
bug core fixed
Milestone
3.8.1

Comments

@cyberduck
Copy link
Collaborator

298fb2c created the issue

When uploading files to ftp server via cyberduck, after update to 3.8, it shows filesize always with 4,0 (or 4,1) GB. But I was uploading a 48,0 MB file. I tested various files with different sizes. It shows always a filesize of 4,0 GB.
Upload doesnt progress after the actual filesize is reached (e.g. 48,0 MB), and will not be completed. No file does appear on my FTP Server.

Attachments
@cyberduck
Copy link
Collaborator Author

bee7825 commented

I have exactly the same issue when uploading files in Version 3.8 (7920)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Bug must have been introduced in d4ef032.

@cyberduck
Copy link
Collaborator Author

lrkirsch commented

After updating to version 3.8, I also experienced the filesize problem when uploading to my Amazon S3 bucket. (I never tried FTP.) So I went back to 3.7, and all is well again. I'm still using OS 10.5.8 if that might matter.

@cyberduck
Copy link
Collaborator Author

depourtales commented

Same issue on 10.5.8 and v3.8 using FTPS transfers. Anyway, all the transfers finish and the files are correctly saved on the target FTPS folder. Uploads are marked as finished

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The root cause of the issue is tracked in Rococoa Issue #3.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you confirm you are running this on a PowerPC (PPC) Mac?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 47ea3af.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please try the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

298fb2c commented

last snapshot build (7929) did fix it! thank you very much.
Bye the way: Forgot to set "architecture" correctly: It is Intel based MacBook Pro.

@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.
Assignees

@dkocher dkocher

Labels
bug core fixed
Projects
None yet
Milestone
3.8.1
Development

No branches or pull requests
2 participants
@dkocher @cyberduck