error: RPC failed; curl 18 transfer closed with outstanding read data remaining

Ulrich Spörlein uqs at
Wed Oct 28 19:54:11 UTC 2020

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.

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 clone 
continue timing out over the next few days, we can have another look.

Sorry for the inconvenience,

More information about the freebsd-git mailing list