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

Resume starts from 'almost' beginning of file #3284

Closed
cyberduck opened this issue Jul 2, 2009 · 5 comments
Closed

Resume starts from 'almost' beginning of file #3284

cyberduck opened this issue Jul 2, 2009 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jul 2, 2009

5b831df created the issue

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 26, 2010

e9310c0 commented

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 :?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 26, 2010

e9310c0 commented

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 24, 2010

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 24, 2010

@dkocher commented

Replying to [comment:3 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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 24, 2010

@dkocher commented

In 41ca052.

@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.
Projects
None yet
Development

No branches or pull requests

2 participants