sapling/eden/fs
Wez Furlong d3202383c1 tidy up journal subscribers on unmount
Summary:
We have a couple of issues with the watchman/eden integration:

1. If you "win" the race, you can cause a segfault during shutdown
by changing files during unmount.  This causes the journal updating
code to trigger a send to the client, but the associated eventBase
has already been destroyed.

2. We don't proactively send any signal to the subscriber (in practice: watchman)
when we unmount.  Watchman detects the eden shutdown by noticing that its
socket has closed but has no way to detect an unmount.

This diff tries to connect the unmount with the set of subscribers and tries
to cause the thrift socket to close out.

Reviewed By: bolinfest

Differential Revision: D6162717

fbshipit-source-id: 42d4a005089cd9cddf204997b1643570488f04c3
2017-10-27 09:01:57 -07:00
..
config Ensure explicit dependency on boost_filesystem 2017-10-18 20:34:41 -07:00
fuse only grab the current time once 2017-10-20 11:42:27 -07:00
inodes tidy up journal subscribers on unmount 2017-10-27 09:01:57 -07:00
journal tidy up journal subscribers on unmount 2017-10-27 09:01:57 -07:00
model add more debug logging of checkout operations 2017-10-25 16:51:56 -07:00
rocksdb use rocksdb column families to separate key spaces 2017-09-07 14:50:42 -07:00
service tidy up journal subscribers on unmount 2017-10-27 09:01:57 -07:00
store unused headers 2017-10-26 11:39:43 -07:00
testharness remove the blocking getSha1ForBlob method 2017-10-18 10:36:29 -07:00
utils move Iterator, Enumerate, EvictingCacheMap, Foreach, Merge, and 2017-10-23 12:30:26 -07:00