From owner-freebsd-git@freebsd.org Thu Oct 29 13:08:53 2020 Return-Path: Delivered-To: freebsd-git@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 300C44509BB for ; Thu, 29 Oct 2020 13:08:53 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CMQkD29fnz3TR8; Thu, 29 Oct 2020 13:08:52 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by mail-oi1-f177.google.com with SMTP id u127so3096965oib.6; Thu, 29 Oct 2020 06:08:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=sJp1s//tkKRYOdrhKZQmCM1Y/n1jzH9b3sSjayOkYmk=; b=tZ1L1XjahixARB2Vw+nzJVd2DAnMn69jrpwMjyxcMbQ5nlv1ryxnOc3yWkfc0eRwoQ Nnp2MJSs16dTy48h4oSnmpQN/mHz1LLJ4Z8Mi7/S1o9jjTWzYsXncouILSqG7XxRd8/7 ID7Oexu7kAGECqNDQp8XnxIkuDvSXVo/nEjVVDkChc1lVvvxSBhVlYuDYtmR9Pk52COG fwgwNkv425wU+XOhbeGNZQpbXN8QfiVOwNftHD2vvd3Qnf/DHb9YIBsKjra2wd1CfDJE 7RFWm4Lc7HtCBBqS11GaO7t8zBca0Rv9lLKGeIQk569fFkYRiV8fVvnmpkZ6Lsh44MVz JoKQ== X-Gm-Message-State: AOAM530GiGek4ELVI5zoZ/Zae/zAp/voZRebzMUKjkBCiGaaR2cvaMaA 5fLGhONrQTEQo7jli5IbKntXBu+SjSFF2sIETkxDioiw X-Google-Smtp-Source: ABdhPJzSWWjJx8WF4keeluHZSJu8pn8/0L1YD6rhfnI00N951SR5V1MFjdu42mzHBpnFnoPb2uPAlMQ2nxCSnWjHqXY= X-Received: by 2002:aca:b141:: with SMTP id a62mr2607905oif.101.1603976929963; Thu, 29 Oct 2020 06:08:49 -0700 (PDT) MIME-Version: 1.0 References: <4260438E-0F95-4A59-8CD1-7DCF47B56D45@FreeBSD.org> <20201028195401.GR92039@acme.spoerlein.net> <6A9E2766-8C64-4880-95CA-990D2589304C@FreeBSD.org> In-Reply-To: <6A9E2766-8C64-4880-95CA-990D2589304C@FreeBSD.org> From: =?UTF-8?Q?Ulrich_Sp=C3=B6rlein?= Date: Thu, 29 Oct 2020 14:08:25 +0100 Message-ID: Subject: Re: https://cgit-beta.freebsd.org/src.git: error: RPC failed; curl 18 transfer closed with outstanding read data remaining To: Dimitry Andric Cc: freebsd-git@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4CMQkD29fnz3TR8 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2020 13:08:53 -0000 On Wed, Oct 28, 2020 at 9:30 PM Dimitry Andric wrote: > > On 28 Oct 2020, at 20:54, Ulrich Sp=C3=B6rlein wrote: > > > > 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 a= ll > >> work fine, even for the FreeBSD repository. Therefore, I am inclined t= o > >> think that some cgit-beta server timeout setting is to blame. > > > > Hi Dim > > > > just to make sure, as you explicitly write "on an already populated > > clone", does this also happen with a fresh clone? > > > > 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 :) > > > > IOW, please try a fresh clone, and if the future `fetches` to this clon= e > > 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? No idea if these were enabled or not. But as I wrote, the aggressive repack= ing has only been turned off last night. So, does the problem currently persist? It would be strange if you're the only one running into this ... Uli