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

Hangs on quit with stale session #3941

Closed
cyberduck opened this issue Nov 20, 2009 · 4 comments
Closed

Hangs on quit with stale session #3941

cyberduck opened this issue Nov 20, 2009 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Nov 20, 2009

169d173 created the issue

i connect using sftp, and edit directly in textmate. quite often my sessions go stale, and saving/uploading fails, but if i hit stop and save again, cyberduck will reconnect and both saves will succeed.

i'm guessing what is happening is that the session has gone stale and cyberduck is trying to end the stale session, but it isnt responding.

a fix would be to find a way to keep the sessions from going stale... maybe with NOOP commands.

i am on a laptop connecting wirelessly, so maybe there is an interruption in signal and that is causing the sessions to break.

i fully plan on donating once this is addressed, because this is my only problem with the program, but for now it's a major one as cyberduck often hangs my machine during restarts...

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 29, 2009

anonymous commented

might be 2 separate tickets...

  1. saves fail when the sessions are stale
  2. program hangs on quit when the sessions are stale

so if you can stop them from stalling out, that fixes both, otherwise, just put code to timeout after 1 second and try to reconnect as if the user clicked the stop icon and then ran the save process in textmate again.

a hacky fix would be to delete the file "cyberduck_deleteme" then create it again, then delete it again. that should ensure a change is made. another setting for that defaulting to 10 minutes would be nice.

in a perfect world you stop the sessions from going stale, or provide options to force activity, and also add checks in the save routine and the quit routine to fix stale sessions.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 10, 2010

169d173 commented

the problem is still in the latest version... still waiting on this fixed. it's very easy for data to be lost if the session is stale and you think you saved a file you were working on, but it was never uploaded to the server.

if i hit the "stop sign" icon, and then go back into my editor and save again, then cyberduck will reconnect. it seems simple to me to detect a disconnect and automate those steps.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 12, 2010

@ylangisc commented

refer to #4214 for 1)

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 29, 2010

@dkocher commented

In 356476b. See also #5073.

Loading

@cyberduck cyberduck closed this Jul 29, 2010
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants