Resume starts from 'almost' beginning of file

[jeanholt@…]

I am not sure if this is as designed - loading 150-250MB files. I can an I/O error after a while or Cyberduck appears to merely stall. (uploading with SFTP) When I click STOP and then RESUME, the resume starts many MB earlier than the amount I have uploaded. i.e. if I have uploaded 90MB and total file size is 100; it appears to start at a random point like '5MB' - I sense that the spot it starts at is the FIRST ATTEMPT spot. i.e. it might have stalled the first attempt @ 5MB. Is this as designed or can I do something to push it further along?

[laas.ee@…]

hi,

i have what i believe to be the same problem. i'll try to explain in more detail though :)

case:

• start upload (sftp)
  
• quit Cyberduck or Stop it
  
• resume upload

result: upload starts at some earlier "milestone" than it actually had progressed prior to quitting app or stopping teh transfer

some pics to explain this also:
1) pic1 - stopped teh transfer (funny people movie) at ~205 MB
2) pic2 - resumed transfer from Transfers window with Resume button ..resumed from ~149 MB
3) pic3 - dropped the Funny movie into teh main browser window to exact dir at server
4) pic4 - voila transfer resumed from ~205 MB

Don't know what exactly causes this, but would be wonderful if someone could please take a look.

Don't know either what the following file is used for ~/Library/Application Support/Cyberduck/Queue.plist

..but mb this one just needs to be updated upon quit/stopping transfer :?

[laas.ee@…]

forgot from the previous comment the client version ..using the latest aka Version 3.4.2 (5902)

[dkocher]

I cannot replicate this in the latest ​snapshot build available. Please reopen if this is still an issue for you.

[dkocher]

Replying to dkocher:

I cannot replicate this in the latest ​snapshot build available. Please reopen if this is still an issue for you.

Actually I can reproduce the issue now.

[dkocher]

In r7763.