From: Duy Nguyen <pclouds@gmail.com>
To: alexander.d.mills@gmail.com
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: concurrent access to multiple local git repos is error prone
Date: Mon, 6 Aug 2018 17:22:47 +0200 [thread overview]
Message-ID: <CACsJy8Dh_u+8VkyCW60PBvieH-L5EMA+DvUDqYMHfbC1=q=S+A@mail.gmail.com> (raw)
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
prev parent reply other threads:[~2018-08-06 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 21:47 concurrent access to multiple local git repos is error prone Alexander Mills
2018-08-04 21:48 ` Alexander Mills
2018-08-05 1:46 ` Jonathan Nieder
[not found] ` <CA+KyZp5i0EXPJ10v+SXmHWCYvZ7=XT8K8gcka0qxCBYXq=OevA@mail.gmail.com>
2018-08-05 6:13 ` Jonathan Nieder
[not found] ` <CA+KyZp4Yc4_Xaw3v+BPwxi_PW75=GXmj=Re7EpsurXi2_hMc9w@mail.gmail.com>
2018-08-05 8:11 ` Jonathan Nieder
2018-08-05 19:17 ` Alexander Mills
2018-08-05 19:34 ` exit code in git diff-index [was: Re: concurrent access to multiple local git repos is error prone] Thomas Gummerer
2018-08-06 7:36 ` concurrent access to multiple local git repos is error prone Alexander Mills
2018-08-06 7:38 ` Alexander Mills
2018-08-06 14:32 ` Jonathan Nieder
2018-08-06 15:22 ` Duy Nguyen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8Dh_u+8VkyCW60PBvieH-L5EMA+DvUDqYMHfbC1=q=S+A@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=alexander.d.mills@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).