Date: Wed, 28 Oct 2020 21:30:18 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: =?utf-8?Q?Ulrich_Sp=C3=B6rlein?= <uqs@FreeBSD.org> Cc: freebsd-git@freebsd.org Subject: Re: https://cgit-beta.freebsd.org/src.git: error: RPC failed; curl 18 transfer closed with outstanding read data remaining Message-ID: <6A9E2766-8C64-4880-95CA-990D2589304C@FreeBSD.org> In-Reply-To: <20201028195401.GR92039@acme.spoerlein.net> References: <4260438E-0F95-4A59-8CD1-7DCF47B56D45@FreeBSD.org> <20201028195401.GR92039@acme.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_9A85CAAB-1773-4DD4-B86A-2B31831EF78E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On 28 Oct 2020, at 20:54, Ulrich Sp=C3=B6rlein <uqs@FreeBSD.org> wrote: >=20 > On Tue, 2020-10-27 at 15:13:09 +0100, Dimitry Andric wrote: >> I consistently get this error when doing a "git fetch", on a already >> populated clone. This is with git 2.28.0, on a FreeBSD 13-CURRENT >> client. On the same system, git fetching over https from e.g. GitHub = all >> work fine, even for the FreeBSD repository. Therefore, I am inclined = to >> think that some cgit-beta server timeout setting is to blame. >=20 > Hi Dim >=20 > just to make sure, as you explicitly write "on an already populated > clone", does this also happen with a fresh clone? >=20 > I think the aggressive repacking between runs is to blame here, as = that > takes away the potential to send a small diff update. I've now = reverted > the aggressive GC and have changed the conversion to run 3x per day = per > repo. (We no longer need the aggressive repack, it was put in place to > fix something else :) >=20 > IOW, please try a fresh clone, and if the future `fetches` to this = clone > continue timing out over the next few days, we can have another look. Yes, this was precisely the advice I got the last time. :) I had my fresh clone then, which is now a little bit less fresh, and I want to update it, that's really all. Am I really expected to clone the whole thing every time...? That said, I'm unsure if you use bitmaps on the server side, which should speed up operations like this. Are these enabled? -Dimitry --Apple-Mail=_9A85CAAB-1773-4DD4-B86A-2B31831EF78E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCX5nU2gAKCRCwXqMKLiCW owXZAJ0TgAch9fO3XQ3ufQOJoAgybiBbrQCgxjKjpSEnAkefO+OvsQ0EahOTYfg= =pHtX -----END PGP SIGNATURE----- --Apple-Mail=_9A85CAAB-1773-4DD4-B86A-2B31831EF78E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6A9E2766-8C64-4880-95CA-990D2589304C>