On Mon, Aug 6, 2018 at 9:38 AM Alexander Mills <alexander.d.mi...@gmail.com> wrote: > Yeah this concurrency problem is real. Not only does it happen with > `git status` the same thing happens with `git rev-parse > --show-toplevel`.
"git rev-parse --show-toplevel" having this same problem helps. This command should never make any update in the repository, not even taking any lock and very basic access to the repository (I think it just needs to resolve HEAD, it does not even access object database). It's so "simple" [1] that makes me think this problem is something not really related to git. Perhaps the process is terminated abnormally because it hits some system limits? [1] well the repo discovery steps are a bit messy but I think it's unlikely we have any racing issues there. > What happens is that I get no stdout when repos are accessed > concurrently (and no stderr). -- Duy
