Race with cmake-server's "dirty" signal
The "dirty" signal is sent by cmake-server to a client when it detects a file affecting configuration is changed. This way a client knows when to re-run configure/generate. It seems that there's a problem, though: libuv reports changes to the CMake files just barely after configure/generate finishes. CMake is being tricked by its own modifications to its own files! As such,
m_isDirty is set to
generate, then immediately reset back to
true, and the "dirty" signal fires again. Because of this, CMake server believes itself to be perpetually in a "dirty" state.