Zeyi (Rice) Fan c78cf6ca3b hgmain: check if EdenFS is running on Windows ... Summary: On Windows, some Mercurial commands may create files in `.hg` directory even if EdenFS is not running. As a result, the command itself will fail while the file still left in the directory. Users typically will then start EdenFS and repeat the same command. However, due to the current design of EdenFS, it will not be able to recognize these files created when it is stopped and return errors for any attempts to write/remove the file, generate another error. Users then need to stop EdenFS and manually remove the file in `.hg` directory to recover the repository. This creates a very bad user experience. The correct way to fix this is to teach EdenFS to track the modifications happened when it is not running, however this will take a few weeks to get there. For a temporary measurement, we teach Mercurial to abort when EdenFS isn't running to avoid trickier recoveries. Reviewed By: quark-zju Differential Revision: D24001090 fbshipit-source-id: abc1ebcdae3819756fe64b5321f52a6e62c0c360		2020-09-30 15:39:34 -07:00
..
eden_apfs_mount_helper	if APFS volume name exceeds 127 length, hash it to avoid failure	2020-07-16 09:17:16 -07:00
hgmain	hgmain: check if EdenFS is running on Windows	2020-09-30 15:39:34 -07:00
scm_daemon	Switch from failure::Fail trait to std::error::Error for errors	2019-11-22 08:53:31 -08:00
scratch	fb-scratch: stop building the package	2020-09-17 18:32:19 -07:00
utils	revisionstore: disallow reading LFS pointers from packfiles	2020-09-09 18:27:42 -07:00