You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every upload is listed as incomplete, X+1KB of XKB transferred.
On each transfer, pressing "Resume" - it authenitcates, does something, then transfer is listed as compled, 0KB of 0KB.
Consistent across all servers (I upload to 2 different servers), all uploads, eavery time.
The text was updated successfully, but these errors were encountered:
I have a similar problem except that I'm testing using a "folder" with hundreds of files. Upon clicking on resume, it reverifies all my fiels and then continues to upload where it left off.
But the incomplete message shows up again after about 5 min or so with no error messages or anything. I have no idea if it timed out, got disconnected, nothing...
Using the latest nightly build from today, and leopard.
I have the similar problem using 2.8.2, excepted that in the previous version (I've just updated my version), all the transfers were incomplete. Now, with this new version, most of the transfers are OK, but I've noticed that the problem occurs when sizes mismatch between local file and distant file. I have the problem when file has not the same size on the server than locally. It's always bigger on the server (for example : 3,8 KB in place of 3,7 KB). But the real number of transfered bytes are the same : 3840 bytes. And the "ls" command shows this value, locally and on the server. Maybe this is because of sector size and different file systems, that the program doesn't care about content file size, but space occupied on the file system.
Every upload is listed as incomplete, X+1KB of XKB transferred.
On each transfer, pressing "Resume" - it authenitcates, does something, then transfer is listed as compled, 0KB of 0KB.
Consistent across all servers (I upload to 2 different servers), all uploads, eavery time.
The text was updated successfully, but these errors were encountered: