Shawn Pearce 685a66ab1e Do not allow index futures to be cancelled ... Once a change is written to the backing store (ReviewDb or NoteDb), it should also be written into the secondary index, even if the user tries to abort the current operation (e.g. presses Ctrl-C on a running `git push`). Don't allow cancellation of a higher level future to go down into the index update future. This also better protects Lucene from seeing an interrupt while using the secondary index and closing the NIOFSDirectory. Change-Id: I8027a6226a5a1f7196506a0388a66d0568f67a5c		2016-08-02 08:33:08 -04:00
..
src	Do not allow index futures to be cancelled	2016-08-02 08:33:08 -04:00
BUCK	Merge branch 'stable-2.12'	2016-06-29 11:17:52 +09:00
BUILD	Implement Bazel build	2016-06-14 21:12:02 +02:00