Cyberduck Mountain Duck CLI

#11639 new defect

Reload of browser after rename operation completes discards current editing state

Reported by: bkazez Owned by:
Priority: normal Milestone:
Component: core Version: 7.8.5
Severity: major Keywords:
Cc: Architecture:
Platform: macOS 11

Description (last modified by bkazez)

  1. Rename a file
  2. Before step 1 finishes, start renaming a second file
  3. After step 1 finishes, the rename session started in step 2 is ended

Expected: I should be able to continue renaming as desired

Change History (7)

comment:1 Changed on Mar 31, 2021 at 12:00:16 AM by bkazez

  • Description modified (diff)

comment:2 Changed on Apr 1, 2021 at 12:01:41 PM by svogt

  • Owner set to svogt
  • Status changed from new to assigned

Hi,

Thanks for reaching out.
Please update to the latest released version of Cyberduck (7.8.5). If the issue persists please tell us the operating system and the protocol that's in use.

– Sofie

Last edited on Apr 1, 2021 at 12:33:37 PM by svogt (previous) (diff)

comment:3 Changed on Apr 1, 2021 at 6:19:41 PM by bkazez

  • Version changed from 7.8.3 to 7.8.5

Still happens on 7.8.5. macOS 11.2.3 + S3.

comment:4 Changed on Apr 7, 2021 at 10:26:23 AM by svogt

  • Owner svogt deleted
  • Status changed from assigned to new
  • Type changed from defect to enhancement

Is reproducible but currently expected behavior.

comment:5 Changed on Apr 7, 2021 at 10:37:28 AM by dkocher

  • Summary changed from Existing rename actions in progress end current rename session to Reload of browser after rename operation completes discards current editing state

comment:6 Changed on Apr 7, 2021 at 10:38:08 AM by dkocher

  • Platform set to macOS 11
  • Priority changed from normal to low

comment:7 Changed on May 13, 2021 at 6:24:55 PM by bkazez

  • Priority changed from low to normal
  • Severity changed from normal to major
  • Type changed from enhancement to defect

If you're renaming many files quickly, then this bug means that files will have the wrong name. It is not useful/expected to end (and save!) an in-progress rename session just because another rename completed. Since this causes loss of user data during a common operation, I increased the severity.

Note: See TracTickets for help on using tickets.