Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
use polling for cache if available #1937
Some remotes support polling for changes on them. As far as I can tell, only drive does this now.
Some issues I found already:
Forgot to link the commit: b33e3f7
Though I do find that the first point still happens: moving a file doesn't seem to expire both parent folders, only the destination
But that seems to be the only quirk. Apart from it, both cache and the vfs cache are told to expire their entries.
referenced this issue
Feb 12, 2018
You are both correct. If there's a large folder then it's going to be a pain to evict each file. Sadly, the entire watch feature I'm using seems to be watching only for folders. There are several ways to improve on this:
I think both of them need to be implemented
@daniel-loader Yep, I'm doing 24h for my personal drive. But I was also using that before, I don't write anything outside the mount.
Go higher, see how it works. If you encounter a scenario where something was changed on drive and it's not reflected after at least 1 minute in cache, let me know so that I can test it.
That sounds like a good idea. The API was developed for the VFS cache so could do with expanding!
I'm still having problems with the new polling feature for cache...
I write to the remote from another machine, on a different network, with
Maybe expiring a top level directory doesn't work correctly? Or maybe the parenthesis in a dir name cause trouble?
I'm running out of ideas otherwise.. It's a single
On my other machine, where I just
Maybe somebody got an idea? Would be more than happy to do some troubleshooting but really don't know where to start :/