-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Removed code to handle GenerateUniqueName bug #9397
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
Conversation
@gave92 Did you want to have a look at this one? I believe you added the original code to handle the bug that was there. From my testing it seems no longer necessary? |
Yep I'll check though I can't remember exactly what the problem was here. Like extracting the same file twice from .zip. |
Ok I was able to reproduce the issue. Steps are:
Not sure what to do about that but sure I have to learn to write better comments -.- |
Ah yeah, the GenerateUniqueName is completely ignored. I'll have another look and see if there is a possible workaround, but if you weren't able to find anything I don't think I will. If that's the case do you want me to just update the comment with this PR or close it out? I wonder if it's because the File object from the dragged zip file doesn't contain a path, so it isn't able to compare correctly. |
A bit of a hacky solution. What are your thoughts @gave92 ? |
I don't like it 😜 but yeah it seems the only solution 👍
Path being empty appears not to be the only factor. When dragging files from Phone storage, path is also empty but GenerateUniqueName works fine. |
@puppetsw do you mind if I tweak your solution slightly? |
Yeah go for it. |
Done, I've made changes so:
|
Looks much better now. I didn’t consider the race condition. Thanks for your help and input. |
Resolved / Related Issues
Items resolved / related issues by this PR.
Details of Changes
Add details of changes here.
Validation
How did you test these changes?
Screenshots (optional)
Add screenshots here.