You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While debugging and trying to list a google drive, if multiple files have the same name exactly, the application crash.
For some reason, GoogleDrive allows multiple files to have exactly the same name.
This is handled here and this check is disabled in release mode.
Steps to Reproduce
Connect to a google drive with two files having exactly the same name and do a op.list(...)
Expected Behavior
I guess the simplest is to completely ignore the file and not crash or simply log an error somewhere.
At least, the error and comment should be more precise.
Additional Context
I'm new to the library, sorry if it's the expected behavior or if there's another issue about it. I couldn't find anything about that.
Are you willing to submit a PR to fix this bug?
Yes, I would like to submit a PR.
The text was updated successfully, but these errors were encountered:
I used to think we should prohibit this case, but I've somewhat changed my mind. I now believe that we can simply permit such cases and only select the newest one while read and returning all of them during the list.
Anyway, we can ignore the file at first. Would you like to help implement it?
Describe the bug
While debugging and trying to list a google drive, if multiple files have the same name exactly, the application crash.
For some reason, GoogleDrive allows multiple files to have exactly the same name.
This is handled here and this check is disabled in release mode.
Steps to Reproduce
Connect to a google drive with two files having exactly the same name and do a
op.list(...)
Expected Behavior
I guess the simplest is to completely ignore the file and not crash or simply log an error somewhere.
At least, the error and comment should be more precise.
Additional Context
I'm new to the library, sorry if it's the expected behavior or if there's another issue about it. I couldn't find anything about that.
Are you willing to submit a PR to fix this bug?
The text was updated successfully, but these errors were encountered: