Ben Gemmill

@chrisidefix On your topic of caching, that's actually what the nodes.db in your ~/.cache folder contains after a sync. Are you seeing performance related issues querying it? I know there...

Addresses issue: https://github.com/yadayada/acd_cli/issues/368

@yadayada looks like the buildbot needs a new oauth token to test properly. I see this in the logs: CRITICAL:acdcli.api.oauth:Invalid authentication token: Invalid JSON or missing key.Token: {"refresh_token": "bar", "expires_in":...

I've implemented proper mtime handling in one of the xattrs so that rsync over acd_cli can work as expected. This addresses: https://github.com/yadayada/acd_cli/issues/58

Turns out that ecryptfs has a subtle bug when it stores its crypto headers in xattrs; it reports file size incorrectly on the next time it's mounted: https://bugs.launchpad.net/ecryptfs/+bug/1612492 That means...

I've finally gotten rsync, ecryptfs, and acd_fuse playing nice together. There were enough corner cases around rsync flags I can't control (thanks Synology!) and some older versions of the kernel...

@Thinkscape I'm only going to pursue the file backing if the write memory backing is too memory intensive. At the moment this PR makes both ecryptfs and rsync work properly,...

@Thinkscape Thanks for clarifying. @jrwr's point as I understood it was what do you do with that temporary file once you're done. Delete it immediately, keep it around for faster...

@Thinkscape It turns out if you run that example you'd see what I did; no real performance hiccups because the docker memory clamping forces the older bits of big buffers...

@Thinkscape short story: you'll want to delete your nodes.db and re-sync. The way acd_cli sync works now is to get changes since a last snapshot, and you'll find that only...