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

Jump to bottom

Maximum simultaneous transfer limit of 1 not properly handled #5624

Closed
cyberduck opened this issue Jan 8, 2011 · 2 comments
Closed

Maximum simultaneous transfer limit of 1 not properly handled #5624

cyberduck opened this issue Jan 8, 2011 · 2 comments
Assignees
@dkocher
Labels
bug core fixed
Milestone
4.0

Comments

@cyberduck
Copy link
Collaborator

613c850 created the issue

I start one tranfer, then start several more. Initially, the maximum transfer limit of 1 is in effect, with the other transers waiting. However, if I stop one of the queued, non-open tranfers, another queued transfer starts. Thereafter Cyberduck behaves as if the maximum transfer limit is 2, until all transfers are complete or stopped and removed from the transfers list.

3.6.* versions didn't exhibit this behavior, but versions 3.8 and higher (including the latest nightly build) do.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

In be5565e.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

You can switch to the latest snapshot build that includes the fix.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug core fixed
Projects
None yet
Milestone
4.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck