Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maximum number of simultaneous transfers not handled properly #11001

Closed
cyberduck opened this issue Mar 24, 2020 · 3 comments
Closed

Maximum number of simultaneous transfers not handled properly #11001

cyberduck opened this issue Mar 24, 2020 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 24, 2020

b87c3bc created the issue

The number of simultaneous transfers is not handled properly. It can end up in not downloading anything anymore while there are still transfers queued. When changing the number in the box at the bottom of the transfers window up and down at some time nothing changes anymore in the real amount of transfers . When some time later all active transfers have ended the transfers still queued are all in the ""maximum allowed connections exceeded. Waiting..." state and none of those transfers are becoming active. So nothing is transfered anymore.

What I have also seen is that the maximum # transfers is set to a certain nunber and there are already more transfers active thenthe nunber is the selct box but when I increase the maximum more transfers become active despite the fact that the number of active transfers was higher than the maximum in the box.

-*[UPDATE v.7.9.0]: When queued transfers in the download box are stopped then resumed, CyberDuck stops limiting the maximum number of transfers allowed. It downloads all transfers simultaneously instead of queuing them.**

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 12, 2021

@dkocher commented

In e619d2e.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 29, 2021

@dkocher commented

Milestone renamed

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 25, 2021

@dkocher commented

Additional fix in 3b0797d.

Loading

@cyberduck cyberduck closed this May 25, 2021
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants