[Cyberduck-trac] [Cyberduck] #7310: Edited file not uploaded after save

Cyberduck trac at cyberduck.io
Sun Jun 14 19:58:12 UTC 2020


#7310: Edited file not uploaded after save
---------------------------+-------------------------
 Reporter:  timsk          |         Owner:  dkocher
     Type:  defect         |        Status:  reopened
 Priority:  normal         |     Milestone:  8.0
Component:  core           |       Version:  7.4.0
 Severity:  normal         |    Resolution:
 Keywords:  editor upload  |  Architecture:  Intel
 Platform:  macOS 10.15    |
---------------------------+-------------------------
Changes (by DrAltoids):

 * status:  closed => reopened
 * cc: bob@… (added)
 * arch:   => Intel
 * platform:   => macOS 10.15
 * version:  4.3.1 => 7.4.0
 * milestone:  4.4 => 8.0
 * keywords:   => editor upload
 * resolution:  duplicate =>


Comment:

 Replying to [ticket:7310 timsk]:
 > I'm having exactly the same problem as described in issue
 [https://trac.cyberduck.ch/ticket/5376 #5376], but that was apparently
 resolved 3 years ago.
 >
 > I connect to an FTP server; I hit cmd-K to edit a file; the file opens
 up in my text editor; I edit the file and save it; and *sometimes* it's
 uploaded back up to the server immediately after saving. Sometimes it
 doesn't. Today, I've just attempted the same edit four times in a row, and
 it won't upload.



 ==== Summary ====
 I have been a licensed user of Cyberduck for years and have this
 experienced this issue for years.  I am experiencing it again.  Please
 don't dismiss this issue.  It is unresolved.  It needs to be fully
 resolved.

   * Cyberduck version:  7.4.0 (32960)
   * Mac OS: 10.15.4 (19E287)
   * Protocol: SFTP
   * Authentication: SSH key
   * Editors tried: Atom 1.48.0 and SubEthaEdit 5.1.3 (9672) -- both
 exhibit the symptoms described below
   * Remote server:
     * Virtualization: kvm
     * Operating System: CentOS Linux 7 (Core)
     * Kernel: Linux 3.10.0-1062.12.1.el7.x86_64
     * Architecture: x86-64


 ==== Symptoms ====

 Open connection to the remote server.  From the file browser, double-click
 on a file to edit it.  It opens as expected in the default browser.  Make
 a change and save... if this is done within a minute or two, the file
 saves locally and uploads as expected.  But if more than a few minutes
 elapse from the time of download, the save will happen locally and the
 upload WILL NOT TAKE PLACE.  If I do not pay careful attention to the
 notification pop-up associated with the upload, or more specifically the
 LACK of pop-up due to the non-uploading of my file, I will lose track of
 changes not actually made to the file on the remote server.  This leads to
 all sorts of issues, not just inconvenience.

 ==== Workaround ====

 IF I catch the fact that the upload did not happen, I select-all in the
 editor window and close the editor's buffer, double-click again on the
 file in Cyberduck to re-open the editor window, select-all, delete, paste,
 save, and watch for the upload confirmation.

--
Ticket URL: <https://trac.cyberduck.io/ticket/7310#comment:5>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list