-
Notifications
You must be signed in to change notification settings - Fork 423
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
Drive refuses to acknowledge certain files are pulled #58
Comments
In about 10 hours I'll get back home and will be able to help out, please let me know any other details, just make sure that no one is editing those files either. If you are sure that the files aren't being modified, you can use '-no-clobber'. The README contains a bit of information that might help you to get started. |
Well I only figured out about double files in my previous post. There were no errors implying that this was a case the application couldn't handle. That said, I removed the duplicate files and the problem is resolved. Should I leave this issue open for documentation purposes/TODO? |
You can close it. |
I have a screenshot of the problem here:
![scr](https://camo.githubusercontent.com/c14c4bd83d76695967192eaa3c172bde70683a3f7dc0d698e9fd85a6b42667be/687474703a2f2f692e696d6775722e636f6d2f316d57545044772e6a7067)
Sorry for the large size, I have a High DPI screen.
The files in the screenshot come from a collaboration project. I can download them through drive, but drive never acknowledges that they're there. The diff states that the files either don't exist locally (which they do) or that the modified dates are different. It will say the same thing right after pulling. The files don't seem to be corrupt. I also didn't touch them, so the fact that the modified dates are different is a mystery to me.
This happened in a huge folder containing subfolders of files. Most files do not suffer this issue. It really is only this set of files. I have already tried removing those files and redownload them, but that doesn't solve it.
I'm having this issue, I can't easily get rid of it, but I have no clue on how to fix it. It might have something to do with Visio and Visio temp files.
The text was updated successfully, but these errors were encountered: