Re: concurrent access to multiple local git repos is error prone

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Aug 5, 2018, 08:11 UTC
Message-ID: <20180805081116.GG44140@aiede.svl.corp.google.com>
In-Reply-To: <CA+KyZp4Yc4_Xaw3v+BPwxi_PW75=GXmj=Re7EpsurXi2_hMc9w@mail.gmail.com>

Alexander Mills wrote:

> Yeah in this case what appeared to be happening is that if `git status` was
> called concurrently, frequently I wouldnt get any stdout..

Thanks for reporting.  A few questions:

What platform are you on? What version of Git are you running? What is the output of "git version --build-options"?

What is the exit status from these "git status" invocations that didn't write output? What options are you passing to "git status"? Are there any other interesting symptoms?

Is this part of a larger tool or script? Are there other operations going on (e.g. something sending signals to these git processes)?

Does the repository pass "git fsck"? Any other symptoms or hints that could help in tracking this down?

Can you paste a transcript of the commands or script you ran and what output it produced? Is this something I should be able to reproduce?

Thanks and hope that helps, Jonathan