git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Duy Nguyen <pclouds@gmail.com>
Date
Aug 6, 2018, 15:22 UTC
Message-ID
<CACsJy8Dh_u+8VkyCW60PBvieH-L5EMA+DvUDqYMHfbC1=q=S+A@mail.gmail.com>
In-Reply-To
<CA+KyZp760a3yTF6ghiNh=c5FoU36MN3cdQU5J8NF2Ss+nwRqyQ@mail.gmail.com>

On Mon, Aug 6, 2018 at 9:38 AM Alexander Mills <alexander.d.mills@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
Previous: Jonathan Nieder
Message 11 of 11 in “concurrent access to multiple local git repos is error prone”
  1. Alexander MillsAug 4, 2018
  2. Alexander MillsAug 4, 2018
  3. Jonathan NiederAug 5, 2018
  4. Jonathan NiederAug 5, 2018
  5. Jonathan NiederAug 5, 2018
  6. Alexander MillsAug 5, 2018
  7. exit code in git diff-index [was: Re: concurrent access to multiple local git repos is error prone]Thomas Gummerer, Aug 5, 2018
  8. Alexander MillsAug 6, 2018
  9. Alexander MillsAug 6, 2018
  10. Jonathan NiederAug 6, 2018
  11. Duy NguyenAug 6, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.