Opened 16 years ago
Last modified 16 years ago
#4457 new Feature request
Persistent Queues
| Reported by: | Doug Jardine | Owned by: | |
|---|---|---|---|
| Priority: | low | Component: | FileZilla Client |
| Keywords: | queues, crash, load, persistence | Cc: | |
| Component version: | Operating system type: | Windows | |
| Operating system version: | Visat 64-bit |
Description
Scenario 1
I had a long queue running, went to bed, checked the machine in the morning.
All files bar two had been successful.
A dialogue box offering an upgrade to 3.2.4 was on top of FileZilla.
I had only had half my first cup of tea for the day, so was a bit slow on uptake and decided I liked the offer of an automatic update, so clicked to carry on with the update.
When FileZilla returned, of course, the queues were all cleared, including the FAILED FILE queue.
Scenario 2
I had a long queue running, went to bed, checked the machine in the morning.
A power failure or crash occurs.
When FileZilla is reloaded, of course, the queues are all cleared.
Unhappy Result
I don't know which files failed to be downloaded.
Pain
I shall now have to hunt down the missing files, and as there is no recursive directory comparison, this will take some time. Alternatively, I could requeue all the files (about 2,000 in many hundreds of directories) and select on-exists=skip-if-same-size.
Possible Solution
PREFERABLE would be for the queues to have been saved as they were processed and restored upon loading FileZilla.
Related Ticket
[4456 is a related ticket | http://trac.filezilla-project.org/ticket/4456]
The failed tab isn't stored on purpose.
The list of queued files is saved in all cases, even on power outages because you are assumed to have a UPS so that your system can gracefully shut down. Crazy to not have one.