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.

Sign up for GitHub

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

Correctly handle file case sensitivity issues in same folder #146

Closed
abraunegg opened this issue Aug 26, 2018 · 2 comments
Closed

Correctly handle file case sensitivity issues in same folder #146

abraunegg opened this issue Aug 26, 2018 · 2 comments
Labels
Bug Something isn't working Fixed

Comments

@abraunegg
Copy link
Owner

Similar to #139 where directory case sensitivity is causing a crash, a similar situation is encountered when a file of the same name is attempted to be uploaded:

Uploading new items of .
Uploading file ./File.txt ... done.
Remaining free space: 5368709115
Requested file to upload exists on OneDrive - local database is out of sync for this file: ./file.txt
Requested file to upload is newer than existing file on OneDrive
Uploading file ./file.txt ... done.

In this case the 'second' file should generate an error message clearly articulating that the file has not been uploaded and that the second local file needs to be renamed before it can be uploaded.
@abraunegg abraunegg added Bug Something isn't working In Progress Currently being worked on labels Aug 26, 2018
@abraunegg abraunegg changed the title Correctly handle file case sensitivity issues Correctly handle file case sensitivity issues in same folder Aug 26, 2018
@abraunegg abraunegg added Fixed and removed In Progress Currently being worked on labels Aug 27, 2018
abraunegg added a commit that referenced this issue Aug 27, 2018
@abraunegg
Resolve Correctly handle file case sensitivity issues in same folder …
ce311db 
…(Issue #146) (#147)

* Resolve to correctly handle file case sensitivity issues in same folder by using the same mechanism as Issue #139
@abraunegg
Copy link
Owner Author

PR merged

@lock
Copy link

lock bot commented Jan 5, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Jan 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Bug Something isn't working Fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abraunegg