All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Charles Diza <chdiza@gmail.com>, git@vger.kernel.org
Subject: Re: Regression in 2.24.1 wrt progress indication
Date: Fri, 13 Dec 2019 23:41:06 +0100	[thread overview]
Message-ID: <20191213224106.GN6527@szeder.dev> (raw)
In-Reply-To: <20191213223554.GA918826@coredump.intra.peff.net>

On Fri, Dec 13, 2019 at 05:35:54PM -0500, Jeff King wrote:
> On Fri, Dec 13, 2019 at 05:21:56PM -0500, Charles Diza wrote:
> 
> > > The bug in question typically showed due to the server side of the
> > > connection. Do you see it during a fetch (or pull) or push? If so, what
> > > server are you using? Is it possible that that server upgraded recently,
> > > and it has nothing to do with what version you're running on the client?
> > 
> > It happens during pull.  I've seen this when pulling from gitlab.
> > Reverting to 2.24.0 fixes the problem.
> 
> gitlab.com is running v2.22.2, which has the bug. And I see it whether
> my client is v2.24.0 or v2.24.1. 

Me too.

> Are you sure it comes and goes between
> client versions?
> 
> Note that it is impacted by your terminal width, as well (it only shows
> up if your terminal is lower than some width; 80 chars, I think).

88 chars.  8 chars of "remote: " prefix + 80 spaces.


      reply	other threads:[~2019-12-13 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 17:28 Regression in 2.24.1 wrt progress indication Charles Diza
2019-12-13 17:38 ` Jeff King
2019-12-13 22:21   ` Charles Diza
2019-12-13 22:35     ` Jeff King
2019-12-13 22:41       ` SZEDER Gábor [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191213224106.GN6527@szeder.dev \
    --to=szeder.dev@gmail.com \
    --cc=chdiza@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.