From: Alexander Mills <alexander.d.mills@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: concurrent access to multiple local git repos is error prone
Date: Sun, 5 Aug 2018 12:17:28 -0700 [thread overview]
Message-ID: <CA+KyZp6KXFfEKNho7njg=0tDxAk-mSMP9r9hZFFH+gZcJ8KptQ@mail.gmail.com> (raw)
In-Reply-To: <20180805081116.GG44140@aiede.svl.corp.google.com>
I am on Ubuntu, I will run the checks that you mentioned. I assume
it's operator error for now though. Like I said, it was just `git
status` that was sometimes failing to send any stdout, presumably when
access to a certain git repo was concurrent, but possibly due to
concurrent access across multiple repos.
Also, as an aside, this seems to be a bug, but probably a known bug:
$ git diff-index HEAD; echo $?
:100755 100755 60e5d683c1eb3e61381b1a8ec2db822b94b9faec
0000000000000000000000000000000000000000 M cli/npp_check_merge.sh
:100644 100644 35a453544de41e2227ab0afab31a396d299139e9
0000000000000000000000000000000000000000 M src/find-projects.ts
:100644 100644 c1ee7bc18e6604cbf0d16653e9366109d6ac2ec9
0000000000000000000000000000000000000000 M src/tables.ts
:100644 100644 29d9674fbb48f223f3434179d666b2aa991ad05a
0000000000000000000000000000000000000000 M
src/vcs-helpers/git-helpers.ts
0
$ git diff-index --quiet HEAD; echo $?
1
different exit codes depending on whether --quiet was used. In this
case, the exit code should be consistent.
The bug is with the `git diff-index` command, as you can see.
-alex
On Sun, Aug 5, 2018 at 1:11 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> 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
--
Alexander D. Mills
¡¡¡ New cell phone number: (415)730-1805 !!!
alexander.d.mills@gmail.com
www.linkedin.com/pub/alexander-mills/b/7a5/418/
next prev parent reply other threads:[~2018-08-05 19:17 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 [this message]
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
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='CA+KyZp6KXFfEKNho7njg=0tDxAk-mSMP9r9hZFFH+gZcJ8KptQ@mail.gmail.com' \
--to=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).