unexpected local_deleted entries about grive

[sgbeal]

PS: i'm an experienced C++ coder, so i'm not afraid to touch code lines to enable/disable debug stuff (but also don't have the energy to dive head-first into grive :/).

[match065]

Are those files exists in gdrive, but not in local?

[sgbeal]

Yes, those are in gdrive, in the same dir as other files which are synced normally. Syncing does not copy these particular files and grive them sees them as local deleted.

Interestingly: the handful of files which have that state all have an update stamp of Apr. 9th in gdrive (the others all have a timestamp from 2010) AND... i see now... they are duplicated in gdrive (WHY gdrive allows multiple independent files with the same name in the same dir, i will never understand). In each dupe pair, one instance has the 2010 timestamp and the other has an Apr. 9th timestamp. In all cases, the docs were uploaded to gdocs no less than 2 years ago.

Weird.

i unfortunately can't collect the relevant details right now but will attach info this weekend.

[nestal]

Any update on this? If not, I will close the issue.

[sgbeal]

the debug output is now off, so i have no idea.

[nestal]

You can get it by running "grive -l log.txt". The log now contains
much more information than before.

[nestal]

Any update on the issue?

[sgbeal]

i apologize, i don't have any new information. i've been too distracted by hacking the past few weeks. i won't have access to my dev machine until the weekend, and will try it out then. Or i'll do this the other way around: i'll close this and re-open it if i can determine that it's still a problem. So far i'm the only one who's commented on it, so it apparently hasn't caused anyone any grief (it didn't seem to break anything on my end, it was just very curious).