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

Upload sequence inconsistency #10514

Closed
cyberduck opened this issue Oct 23, 2018 · 3 comments
Closed

Upload sequence inconsistency #10514

cyberduck opened this issue Oct 23, 2018 · 3 comments
Labels
bug core wontfix

Comments

@cyberduck
Copy link
Collaborator

2ee47a5 created the issue

Hello,

Can you please tell me why my uploads aren’t going out in sequence ?

I haven’t had this problem previously, and it’s totally inconvenient for multiple reasons and strongly leads me to go elsewhere.

Just to be clear, for many years, anytime I did an upload it would progress alphabetically and chronologically from folder to folder.
First, it would upload the folder that went first in the alphabet, and then it would upload the sub-folder first in the alphabet starting
with the lowest numbered image in that folder. Now it's all over the place. It might upload a folder starting with "M" before "A" and
then progress to uploading number 132 before number 25.

What gives, and how can I get back to the conventional A-Z / 01-99 sequencing for my uploads so I know what's already transmitted ?

Thanks for your time !

All The Best,
Daniel
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Set the option to use a single connection for transfers.

Open single connection. Use a single connection to transfer files from a transfer sequentially.

@cyberduck
Copy link
Collaborator Author

2ee47a5 commented

Your vague response was unsuccessful. Images continue to upload out of chronological order after setting my preferences the way described in the link you provided.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The ordering for files uploaded inside a single folder is indeed arbitrary. However we have no intent to sort the ordering – even if lexicographically it would not match your view in the file explorer where you might have the files sorted by modification date or other attribute.

@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
No one assigned
Labels
bug core wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck