drive.changes.list API no longer being correctly processed

[natoriousbigg]

Looks like node-drive-fuse is no longer processing drive.changes.list correctly. New files are added correctly, but when I delete or rename files on the webui, it's not being updated in node-drive-fuse. Deleted files are not being removed node-drive-fuse and when trying to be access, you'll get an I/O error. When files are renamed, both the old name and new name shows up in node-drive-fuse.

[dany20mh]

The only workaround I have for this problem is that make all your changes in bulk and then delete all the files in the cache/data folder, and then remount.

This will make it to recapture the whole thing and you will have a fresh changes.

[hjone72]

I haven't been able to recreate this. I created a folder in the root "test" then created a file under that called "test.log". Waited for Node to see the change, which it did. Tailed the file. Renamed the file to "test1.log" and waited for node to see the change. "test.log" was removed from the directory and "test1.log" was now there.

[natoriousbigg]

@hjone72 Was wondering if you can take a look at this again. I'm still having this issue, and it might be because of my setup. I'm running node-gdrive-fuse on one server and plexdrive on a 2nd server. I'm using plexdrive on the 2nd because it has renaming and deleting capacity (I tried doing on node-gdrive-fuse and it crashes the entire mount). When I rename a file on plexdrive, the changes isn't picked up on node-gdrive-fuse. I no longer have issue with the duplicate files but the renamed files isn't showing up at all on node-gdrive-fuse.

[natoriousbigg]

I'm getting a bunch of these errors in the log for files that are delete/renamed and no longer available:

{"level":"debug","message":"starting to download xxxx, chunkStart: 0","timestamp":"2017-09-08T13:39:34.697Z"}
{"level":"error","message":"The file \"xxxx\" could not be found on Google's server. It's likely to have been deleted.","timestamp":"2017-09-08T13:39:35.259Z"}

[hjone72]

Enable debug logging and watch the log, every 60 seconds or so you should see a log appear that looks something like this:

2017-9-11T6:26::41 - debug: Getting changes from Google Drive. The last change id was 11123194.
2017-9-11T6:26::41 - debug: There was 0 to parse
2017-9-11T6:26::41 - debug: Finished parsing changes from google

When a file changes you should get a slightly different log:

2017-9-11T6:21::16 - debug: Getting changes from Google Drive. The last change id was 1112397.
2017-9-11T6:21::16 - debug: There was 2 to parse
2017-9-11T6:21::16 - debug: somefile.ext is a new file
2017-9-11T6:21::16 - debug: saving folder tree
2017-9-11T6:21::24 - debug: someOtherfile.ext is a new file
2017-9-11T6:21::24 - debug: Finished parsing changes from google

Could you confirm this is what you are seeing?