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...
The text was updated successfully, but these errors were encountered:
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.
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.