I noticed maybe not so important, but annoying problems with FTP connections.
First - every time I trying to copy file and press Abort, i see this:
And it is shown forever until i press Abort here.
Second - Opus sometimes hangs while copying files from FTP. Pressing Abort, then repeating operation resolves problem but still... I think Opus should detects problem like that (no response or freeze transfer) like other FTP clients do.
And third (small question) - sometimes more than 1 simultaneous transfers will be very helpful. Can we expect that feature?
Nothing interesting is in log window because hangs means that nothing happens. Is not any error there, not even info like "waiting for server resonse" etc. Just simply freeze that force me to press Abort, then repeat operation. I check the same with FileZilla and I noticed that FZ can recognize problems like that because even if freezes happens (some slower ftp server responses), they're unfreeze after few seconds, not like Opus which can be suspended by 3 minutes or more and still can't recognize that something is wrong.
PS. Ah, AV/FV compatibility mode, not Opus. It has "disable" mode, can track connections, can show transfers etc. - everything that normal FV should has. No paranoid mode.
Have you tried toggling pasv mode for the site in Opus? Don't know if it'll help, since it seems to be working sometimes, but it might be worth a quick try (e.g. if some ports work and others don't).
It can be any mode and reason can be different, but IMHO there is no point for looking where is a problem, but made universal solution. If I copy 1000 files and after 100 or 200 connection freeze or if I copy one big file and connection freeze after I pressing Abort, then Opus should detect that something is wrong (no transfer and no response but Opus still wait for something? strange). Is easier to made filemanager better than save the world by fixing all possible problems with connections. If FileZilla can do that and can resolve problems with FTP connections (any type, any reason) then Opus should made it too.
I really prefer to go shopping or watch a movie while Opus copying 10 000 files from FTP instead of watching my computer screen. If I can press Abort and then press copy again and it works, then why Opus can't do it for me? It's only suggestion of course.
Without knowing what causes the problem, we can't fix the problem.
Is the issue just that Opus has a longer timeout before it gives up compared to Filezilla, or is something different happening? Is the same thing even happening to Filezilla? (i.e. Is Filezilla handling the problem better, or is the problem not happening at all with Filezilla, due to some other difference?)
Any idea why the connection freezing up in the first place, and how we might re-create it on our own machines/sites?
I disagree. Without knowing what causes the problem, you can fix the problem even better. If you'll know what is the problem, you'll make fix only for that problem, not for other, but similar. It's like AV software - people discover few years ago that database with viruses is not enough and they creates heuristic methods. So if you detect in Opus that is no transfer, no server answer and Opus still wait for something, that means something is wrong and need to be fixed.
I don't know Opus has longer timeout or not - i never wait too long looking at freezed dialog box. In 2012 even 2 seconds respond from server is too long. It's not slow modem era, servers doesn't respond longer than few seconds.
In FileZilla problems like that exists too - sometimes when I copying thousand of files, one connection freeze for few seconds, but after few seconds FZ can handle it.
Without knowing how to re-create the problem on our machines we can only guess at what might be going wrong in the thousands of lines of code involved. Even if we did guess correctly, we would have no way to test our guess, because we don't know how to reproduce the problem.
Sometimes it is easy to guess, but only with very simple code. FTP is not simple. FTP is very complex. Especially when you consider the involvement of 3rd party servers (which often have their own quirks that further complicate things), networks, firewalls, problems that require specific timing to re-create, and so on. That is too many unknowns for us to simply guess where the problem is and solve it with no information other than that you see FTP connections freeze on your machine with your FTP site(s).
I'm not saying that we cannot improve the way Opus handles whatever is happening, but to do so we need more information and a full understanding of whatever is going wrong. We don't have magic problem-solving pixie-dust that we can sprinkle on the code to automatically fix any problems. If we did we'd be millionaires and the code would already perfectly handle ever possible situation.
I only want to say that problem with FTP may be creating by many reasons. I don't even know how can I give you possibility to reproduce problem if problem exists every time I use FTP but I do not made any magic moves or have standard settings. That can be anything as I suppose, including my router (for example) so I can't send you my computer with everything that is connected to. It just happens and I do not expect that you solve all my problems with all possible connections. I only expect that using DOpus i can expect a little less program-user interaction. I don't want sit all the time by computer and watch how files are copying, because that is soo boring (for me of course, maybe someone like that). Programs should be a little smart imho, so please answer me - if FTP transfer is stopped, nothing happens by many seconds (or minutes) and opus still wait for complete operation, then is any reason to keep that freezing process working? What can happens after 2 minutes? Why some "timeout" and "retry" fields can't be add in FTP settings? That don't resolve any problems, of course, but can improve handling of unexpected situations.
Opus already has timeouts on the connections. (e.g. Pull out the network cable and Opus won't wait forever.) In this case it seems something is going wrong, but we need to know more to understand what is going wrong and where to look to solve the problem.
Understanding why the server/connection is freezing/timing out -- in both Opus and Filezilla -- or how to make another server do the same thing should help us understand the problem.
I believe that Opus has timeouts, but they're huge as I suppose and user can't change them in config. Also there is no automatic actions (repeats etc.) that user can set before problem starts (for example - i start copying 10 000 files to/from FTP and go shopping, then after 200 files something happens and Opus ask me what I want to do; I always answered "Retry" few times, then "Abort", so if in config I have fields "number of retries" or at least "default action" then Opus can at least try take typical action without my interaction).
I really want to help but don't even know how to start, so this not so clear problem description is all I can give.
Anyway - I think problem is that server stop answering. If I unplug cable, i'll receive error, nosignal etc. If server stop answering, then Opus receive nothing. Maybe that's reason why Opus wait so long.
And how that can help improving Opus?
Maybe programs for freaks should work only in perfect environment. There are also people who think that browsers should display only pages written in perfect W3C valid HTML, but I prefer when my browser display proper bad written pages too and the same way I prefer when my filemanager and ftp client can handle some basic problems and work even on not so great FTP sites. And I, as user, don't really must know how FTP/computer works. I report bug (at least I think that is a bug) and maybe that helps, maybe not, but at least I try.
The Dopus devs are first rate, and do a fantastic job. But they can't do it without being able to narrow down the truly infinite number of possible variables and recreate the problem. If you want to help them help you, you have to help give them the data they'll need to analyze and resolve.
