Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
modules/kvs: Fix potential to exceed nprocs #1304
@@ Coverage Diff @@ ## master #1304 +/- ## ========================================== + Coverage 78.22% 78.24% +0.02% ========================================== Files 154 154 Lines 27931 27935 +4 ========================================== + Hits 21848 21859 +11 + Misses 6083 6076 -7
At the moment this is not the case, all fences stay on the hash until the fence/commit is done (may it be done by success or error). I think this is what is desired. Because fences are identified by name, we don't want two fences with the same name lingering around.