Cyberduck Mountain Duck CLI

#7791 closed defect (fixed)

Resume not possible after local file not found

Reported by: mers Owned by: dkocher
Priority: normal Milestone: 4.4.5
Component: core Version: 4.4.3
Severity: normal Keywords:
Cc: Architecture:
Platform:

Description (last modified by mers)

I had stopped an upload of a large file from an external drive to S3. I clicked resume without realising my external drive was unmounted. Cyberduck predictably showed an error message. It unpredictably marked the file as 0 bytes with status upload complete. The status should have been left as is on an error, allowing me to mount the drive and resume.

This obviously applies to whatever other addressable errors could cause a resume to fail, the mounting issue just happens to be what caused it for me.

Change History (5)

comment:1 Changed on Feb 13, 2014 at 1:14:23 AM by mers

  • Description modified (diff)

comment:2 Changed on Feb 13, 2014 at 11:02:08 AM by dkocher

  • Milestone set to 4.4.4
  • Owner set to dkocher
  • Status changed from new to assigned
  • Summary changed from resume not possible after error to Resume not possible after local file not found

comment:3 Changed on Feb 13, 2014 at 11:05:31 AM by dkocher

  • Resolution set to fixed
  • Status changed from assigned to closed

In r14334.

comment:4 Changed on Jun 4, 2014 at 2:37:33 PM by dkocher

  • Milestone changed from 4.4.4 to 4.4.5
  • Resolution fixed deleted
  • Status changed from closed to reopened

Reverted in r14713.

comment:5 Changed on Jun 4, 2014 at 2:54:01 PM by dkocher

  • Resolution set to fixed
  • Status changed from reopened to closed

New fix in r14714.

Note: See TracTickets for help on using tickets.
swiss made software