You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I went back to 4.4.4 for now, standard cyberduck.io download.
Some things 4.5 was doing, as of your most recent version. Several of these look like regressions to problems there have been before on prerelease versions, so wondering if you might not be working on the intended Git branch?:
crashing, no sense as to when, just after a while of operations
falsely indicating uploads in particular had not completed. Sometimes downloads.
going a bit berserk other times in large multi-item transfers, then actually failing them; again I think uploads may have been the main task failing. It was giving me some kind of did I want to try again message about listing directories in the middle of a transfer set. I finally checked the box not to bother me about these, but it didn't help the result.
-note that these problems are on 4.5, not on 4.4.4 as newticket insists on limiting me to.
-on a few quick tests, 4.4.4 appears not to have any of these problems, and I have I think quite a stable Win8.1 system, up-to-date as of Tuesday, and always kept that way
The text was updated successfully, but these errors were encountered:
Yes we are aware that snapshot build are sometimes unstable and in particular the Windows build is out of date. The upload incomplete regression was fixed in 829ee00.
I went back to 4.4.4 for now, standard cyberduck.io download.
Some things 4.5 was doing, as of your most recent version. Several of these look like regressions to problems there have been before on prerelease versions, so wondering if you might not be working on the intended Git branch?:
-note that these problems are on 4.5, not on 4.4.4 as newticket insists on limiting me to.
-on a few quick tests, 4.4.4 appears not to have any of these problems, and I have I think quite a stable Win8.1 system, up-to-date as of Tuesday, and always kept that way
The text was updated successfully, but these errors were encountered: