Skip to content
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

filesystem information does not update properly #39

Closed
dellipse opened this issue Jan 2, 2015 · 3 comments
Closed

filesystem information does not update properly #39

dellipse opened this issue Jan 2, 2015 · 3 comments

Comments

@dellipse
Copy link
Contributor

dellipse commented Jan 2, 2015

I am noticing items that should NOT be getting updated are showing up in the log as updated in Google Drive, but items that SHOULD be getting updated (new items from outside sources) are not showing up after well over an hour using the default settings for refresh rate.

EricTheMagician added a commit that referenced this issue Jan 2, 2015
@EricTheMagician
Copy link
Owner

I'll check this again.
It was working for me, but maybe I need a different test case.

For files that " should NOT be getting updated", are you sure that those are not new files that were recently uploaded to GDrive and that google is maybe accessing those files to convert it?
Simply accessing a file or folder on google drive can cause a file to be updated (notably, the last date accessed field).

@dellipse
Copy link
Contributor Author

dellipse commented Jan 3, 2015

That could be the case for files that are "updated" when something is just accessed.

However, after over 24 hours, it still has not detected a folder and its associated contents that were added by another client.

@wnielson
Copy link

I am observing similar behavior and I believe I have identified the issue. In the function parseChanges (here), it appears that the parent items are not being updated to include the new child element.

wnielson added a commit to wnielson/node-gdrive-fuse that referenced this issue Jan 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants