-
Notifications
You must be signed in to change notification settings - Fork 91
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
File size is different after upload ! #260
Comments
Just created another file with 2mb of predictable content like :
Upload it again. The sequence is fine from 1 to 63,594, but there is no data afterward (it should upload until 116,224). So, half of the file seems unwritten. I don’t understand why this code doesn’t throw some sort of error if it’s unable to upload the file completely. Maybe a simple check can be added to compare the file size and the data written. At the very least, it should throw a more meaningful message instead of silently stating that the data transfer is finished when it’s not. |
I have the same issue or a similar issue, when it uploads file some bytes disapears. |
Finally, the mine was not an issue, it is an issue from Filezilla, it treats my file as text. After suffixing extension by .bin it is not corrupt anymore. |
Describe the bug
Just a basic file upload compelte with no error but the file size is different after upload and the file is corrupt.
on server :
on local device :
Can not open the file after download :
Example code
Console output
From the log you can see somehow it immediatel jump to 1245184 but the thing is every time I run the code the output size is different
Which version of Node.js are you using?
Node : v22.11.0
Which version of basic-ftp are you using?
5.0.5
Additional context
Running in windows
The text was updated successfully, but these errors were encountered: