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

Wrong file size displayed for upload #5508

Closed
cyberduck opened this issue Dec 6, 2010 · 5 comments
Closed

Wrong file size displayed for upload #5508

cyberduck opened this issue Dec 6, 2010 · 5 comments
Assignees
Labels
bug ftp FTP Protocol Implementation high priority worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

a0fd505 created the issue

It looks like it just keeps going beyond the file size of the file.

external image

But actually I think what's happening is Cyberduck is capping the file size at 2.9 GB, when actually the file is more than that.

This has only started happening in the latest version of Cyberduck.

The file in this case was an 8.53 GB MKV file being transferred locally via FTP to a hard drive.

I hope you can fix this!

Thanks.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you let me know if you can replicate this issue with the latest snapshot build.

@cyberduck
Copy link
Collaborator Author

a0fd505 commented

Replying to [comment:1 dkocher]:

Can you let me know if you can replicate this issue with the latest snapshot build.
Different problem this time: http://cl.ly/2t3o152w2R09272c1J2g

Very slow upload bandwidth (I don't think it's a local network issue) and it says 7.9 GB instead of the 8.35 GB that it really is.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 stephenc]:

Replying to [comment:1 dkocher]:

Can you let me know if you can replicate this issue with the latest snapshot build.
Different problem this time: http://cl.ly/2t3o152w2R09272c1J2g

Very slow upload bandwidth (I don't think it's a local network issue) and it says 7.9 GB instead of the 8.35 GB that it really is.

There is no change in that build that would change the bandwidth usage.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 stephenc]:

Replying to [comment:1 dkocher]:

Can you let me know if you can replicate this issue with the latest snapshot build.
Different problem this time: http://cl.ly/2t3o152w2R09272c1J2g

Very slow upload bandwidth (I don't think it's a local network issue) and it says 7.9 GB instead of the 8.35 GB that it really is.

Are you running Mac OS X 10.5? Then the difference is explained that in Cyberduck, the decimal file size is displayed but the Finder uses binary. Fixed in 7d3126e that only on 10.6+ decimal file sizes are used.

@cyberduck
Copy link
Collaborator Author

a0fd505 commented

Replying to [comment:5 dkocher]:

Replying to [comment:3 stephenc]:

Replying to [comment:1 dkocher]:

Can you let me know if you can replicate this issue with the latest snapshot build.
Different problem this time: http://cl.ly/2t3o152w2R09272c1J2g

Very slow upload bandwidth (I don't think it's a local network issue) and it says 7.9 GB instead of the 8.35 GB that it really is.

Are you running Mac OS X 10.5? Then the difference is explained that in Cyberduck, the decimal file size is displayed but the Finder uses binary. Fixed in 7d3126e that only on 10.6+ decimal file sizes are used.

No, I'm using 10.6.5 and haven't ever had problems with Cyberduck before this release.

http://cl.ly/2u0C301s1Q1j2q1S3Y2m

@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 ftp FTP Protocol Implementation high priority worksforme
Projects
None yet
Development

No branches or pull requests

2 participants