From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/zh_CN: add docs-next checkout workaround
Date: Sun, 12 Jul 2026 21:42:39 +0800 [thread overview]
Message-ID: <alOZzy3Hk3CEN7ZX@wyuan.org> (raw)
In-Reply-To: <8f01e453-6a4b-4f35-b533-55d89c1a9ae4@hust.edu.cn>
On Sun, Jul 12, 2026 at 04:35:21PM +0800, Dongliang Mu wrote:
> > GIT_TRACE=1 \
> > GIT_TRACE_CURL=1 \
> > GIT_CURL_VERBOSE=1 \
> > git clone https://mirror.nju.edu.cn/git/kernel-doc-zh.git/
> >
> > [...many verbose outputs]
> > remote: Enumerating objects: 11675982, done.
> > remote: Counting objects: 100% (11675982/11675982), done.
> > remote: Compressing objects: 100% (2008049/2008049), done.
> > 13:24:10.505880 http.c:994 == Info: HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> > 13:24:10.505973 http.c:994 == Info: Connection #0 to host mirror.nju.edu.cn left intact
> > error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> > error: 6191 bytes of body are still expected
> > fetch-pack: unexpected disconnect while reading sideband packet
> > fatal: early EOF
> > fatal: fetch-pack: invalid index-pack output
>
> It seems like the same issue with our mirror site. I've forward this email
> thread to NJU mirror maintainers.
Very much appreciated. They might obtain more useful information from
their server logs.
>
>
> > From the output, it seems that there was an error in the mirror of NJU's
> > nginx, the Git HTTP backend behind nginx, or the upstream connection
> > between them, but I'm not 100% sure.
> >
> > I will conduct several more tests immediately to troubleshoot the
> > problem, to see where exactly the problem lies.
> >
> > In addition, cloning with a cloud server in Hong Kong:
> >
> > Cloning into 'kernel-doc-zh'...
> > remote: Enumerating objects: 11675982, done.
> > remote: Counting objects: 100% (11675982/11675982), done.
> > remote: Compressing objects: 100% (2008049/2008049), done.
> > error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: INTERNAL_ERROR (err 2)
> > error: 3965 bytes of body are still expected
> > fetch-pack: unexpected disconnect while reading sideband packet
> > fatal: early EOF
> > fatal: fetch-pack: invalid index-pack output
>
>
> I tried the NJU mirror in my laptop, and successfully clone the repository
> from NJU mirror. There must exist some unknown reason to lead to this
> failure.
Ah, I'm starting to doubt on my side now...
Anyway, I'll check again.
Thanks!
prev parent reply other threads:[~2026-07-12 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 15:25 [PATCH] docs/zh_CN: add docs-next checkout workaround Weijie Yuan
2026-07-10 13:21 ` Dongliang Mu
2026-07-10 13:36 ` Weijie Yuan
2026-07-10 13:44 ` Dongliang Mu
2026-07-10 13:57 ` Weijie Yuan
2026-07-10 14:04 ` Dongliang Mu
2026-07-12 4:47 ` Dongliang Mu
2026-07-12 5:45 ` Weijie Yuan
2026-07-12 6:53 ` Weijie Yuan
2026-07-12 8:35 ` Dongliang Mu
2026-07-12 13:42 ` Weijie Yuan [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=alOZzy3Hk3CEN7ZX@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox