Opened 11 years ago

Last modified 11 years ago

#4497 new Bug report

Reset and reque doesn't work properly

Reported by: mariush Owned by:
Priority: low Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version:

Description

If for some reason there's a problem transferring a file (for example drive full or connection timeout to server) it's moved to the "Failed transfers" tab.
However, when I select the files and click "Reset and re queue files" or whatever is named, the files are moved back to the queue but they don't begin to resume.

For example, if Filezilla is configured to use three download threads and I transfer three files and one file transfer fails, the other two threads continue to download.

If I click "Reset and reque..", file gets moved back to the queue but Filezilla doesn't resume the file. If I want it to be resumed, I actually have to click on Process queue to stop all, and click Process queue again to have it resume. Or, I could just delete from the queue a file above the requeued and Filezilla will pop up the Resume dialogue.

When I choose Reset and requeue I think it's safe to assume I already solved the problem for which the transfer failed in the first place, so it should attempt to resume automatically if a download thread is available.

Perhaps it should even be placed in queue above other files currently transferred and should be resumed as soon as a download thread is available, because if there's some temporary problem (several server resets for example) there would be many partial files filling user's drive.

Change History (1)

comment:1 Changed 11 years ago by mariush

This is especially problematic when, for example, some large file fails for lack of space on drive and you make room and re-queue the file but it's not actually downloading, and you can't stop the current transfers because they're from some weird FTP server which doesn't support resume.
So I have to wait for a slow ftp server without resume to finish before resuming the large file.
I don't know about others but in my case it does happen often.

Note: See TracTickets for help on using tickets.