From: Taylor Blau <email@example.com> To: Son Luong Ngoc <firstname.lastname@example.org> Cc: Taylor Blau <email@example.com>, firstname.lastname@example.org, Jeff.Hostetler@microsoft.com Subject: Re: Git pull stuck when Trace2 target set to Unix Stream Socket Date: Mon, 13 Apr 2020 11:23:16 -0600 [thread overview] Message-ID: <20200413172316.GA63249@syl.local> (raw) In-Reply-To: <D350F464-61DE-4EB6-BBE1-514A0C051F38@gmail.com> On Mon, Apr 13, 2020 at 07:19:03PM +0200, Son Luong Ngoc wrote: > Hi Taylor, > > Thanks for the swift reply. > > > On Apr 13, 2020, at 18:00, Taylor Blau <email@example.com> wrote: > > I doubt that this is important (for a reason that I'll point out below), > > but it looks like your invocation here is malformed with the trailing > > pipe character. > > > > Did you mean to redirect the output of rm away? If so, '2>&1 >/dev/null' > > will do what you want. > It was an emailing mistake. I meant to write > > rm /tmp/git_trace.sock || true For what it's worth, 'rm -f' would suffice, too, but it doesn't matter. > So that the command is reproducible on repeated run. > I must have deleted the remaining part by mistake. > > > Odd. From my memory, trace2 will give up trying to connect to the socket > > (disabling itself and optionally printing a warning) if 'socket(2)' or > > 'connect(2)' set the error bit. My guess above is that you don't have a > > listening socket (because your shell is waiting for you to close the > > '|'), so there's no connection to be made. > There is definitely connection still, as I can still receive more events after interupting the stuck git command by Ctrl-C. > > > Odd. What version of Git are you using? Your description makes it > > sound like it may be a bug, so I'd be curious to hear Jeff's > > interpretation of things, too. > 2.26.0 built from Master git/git > > For more info, I have created a paste to demonstrate the bug > https://gist.github.com/sluongng/e14563e4ce3cc9545781ecd5a95169f6 > In which, I run `git pull origin` and `git version` on a relatively stale https://gitlab.com/gitlab-org/gitlab.git local copy. > > You can get more information from the trace in that paste. > I have annotated the moment which the stuck happened with `It stucks HERE` phrase so look for it. Hmm. It sounds like maybe there is a bug. If Jeff doesn't have time to take a look, I'll try to figure out what's going on here. > Cheers, > Son Luong. Thanks, Taylor
next prev parent reply other threads:[~2020-04-13 17:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-13 12:05 Son Luong Ngoc 2020-04-13 16:00 ` Taylor Blau 2020-04-13 17:19 ` Son Luong Ngoc 2020-04-13 17:23 ` Taylor Blau [this message] 2020-04-13 17:18 ` Jeff King 2020-04-13 18:42 ` Jeff Hostetler
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=20200413172316.GA63249@syl.local \ --firstname.lastname@example.org \ --cc=Jeff.Hostetler@microsoft.com \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Git pull stuck when Trace2 target set to Unix Stream Socket' \ /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
Code repositories for project(s) associated with this 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).