Grive2 fails to identify identical filenames from drive

[susmitgit]

Ways to replicate this issue: Take two different images and give them same name like file_1.jpg. Upload both the files in same google drive folder. It allows by google to keep two separate files in same name. Now run Grive2 and you will get only one on them in the sync result.

[rautamiekka]

I'm not a dev, but how is your computer supposed to have those files in the same folder when they're differentiated by their name and it's identical ?

Nitpicking which doesn't help the problem: I can think of 2 ways Google Drive implements it: 1) each file is stored in a database and they're given an unique value that's mapped to their filename. 2) each file is physically stored using a hash as the filename which is mapped in a database to the actual filename.

[brianborchers]

My perhaps related issue is that grive creates duplicate copies of files in my google drive folder. e.g file.ext exists on my system and in google drive, I run grive to sync files, and now there are two copies of file.ext in google drive.

[prauscher]

If you have Google Photos integrated in your Google Drive, multiple files having the same path might happen some time, as Google Photos will save modified copies (e.g. auto-rotated image) with the same path, creating a duplicate. Additionally, grive2 will try to download this path in every run, so this might be a duplicate of #171