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

Cannot get transfers limited to 1 #5629

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

Cannot get transfers limited to 1 #5629

cyberduck opened this issue Jan 10, 2011 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

c4aee66 created the issue

When I set Cyberduck to a maximum limit of one transfer, I would normally expect to start one transfer and then be able to queue up additional transfers which would wait until the first transfer is finished. However, what I see is that initiating a second transfer actually starts the transfer instead of waiting.

In other words, setting the transfer limit to 1, always allows 2 transfers. Additional transfers after two will always wait as expected. Basically there is no way to have only one transfer and to queue the rest at the same time.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #5624.

@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.
Projects
None yet
Development

No branches or pull requests

1 participant