Cyberduck Mountain Duck CLI

#3284 closed defect (fixed)

Resume starts from 'almost' beginning of file

Reported by: jeanholt@… Owned by: dkocher
Priority: high Milestone: 3.8
Component: core Version: 3.0.1
Severity: blocker Keywords:
Cc: Architecture:
Platform:

Description

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?

Attachments (4)

pic1.jpg (44.3 KB) - added by laas.ee@… on Apr 26, 2010 at 7:42:33 AM.
pic2.jpg (43.9 KB) - added by laas.ee@… on Apr 26, 2010 at 7:42:46 AM.
pic3.jpg (77.2 KB) - added by laas.ee@… on Apr 26, 2010 at 7:42:59 AM.
pic4.jpg (64.5 KB) - added by laas.ee@… on Apr 26, 2010 at 7:43:11 AM.

Download all attachments as: .zip

Change History (10)

Changed on Apr 26, 2010 at 7:42:33 AM by laas.ee@…

Changed on Apr 26, 2010 at 7:42:46 AM by laas.ee@…

Changed on Apr 26, 2010 at 7:42:59 AM by laas.ee@…

Changed on Apr 26, 2010 at 7:43:11 AM by laas.ee@…

comment:1 Changed on Apr 26, 2010 at 7:56:34 AM by 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 :?

comment:2 Changed on Apr 26, 2010 at 8:06:29 AM by laas.ee@…

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

comment:3 follow-up: Changed on Nov 24, 2010 at 5:08:49 PM by dkocher

  • Milestone set to 4.0
  • Resolution set to worksforme
  • Status changed from new to closed

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

comment:4 in reply to: ↑ 3 Changed on Nov 24, 2010 at 5:14:27 PM by dkocher

  • Resolution worksforme deleted
  • Status changed from closed to reopened

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.

comment:5 Changed on Nov 24, 2010 at 5:14:42 PM by dkocher

  • Component changed from sftp to core

comment:6 Changed on Nov 24, 2010 at 5:29:13 PM by dkocher

  • Resolution set to fixed
  • Status changed from reopened to closed

In r7763.

Note: See TracTickets for help on using tickets.
swiss made software