Re: [PATCH] docs/zh_CN: add docs-next checkout workaround

[Weijie Yuan <wy@wyuan.org>]

On Sun, Jul 12, 2026 at 12:47:16PM +0800, Dongliang Mu wrote:
> Hi Weijie,
> Could you please try cloning
> https://mirror.nju.edu.cn/git/kernel-doc-zh.git/ <https://link.wtturl.cn/?target=https%3A%2F%2Fmirror.nju.edu.cn%2Fgit%2Fkernel-doc-zh.git%2F&scene=im&aid=582478&lang=zh>
> and verify whether this mirror is stable?

OK, I just did a quick test on my debian 13 (local physical server):

$ git clone https://mirror.nju.edu.cn/git/kernel-doc-zh.git/
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: 7397 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

then again:

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

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

> TUNA has limited storage capacity and has asked the NJU mirror site to host
> this Git repository.

Fully understand, easy to notice that TUNA is under big preesure these days.
Thanks, NJU!

> We are currently diagnosing network issues on our mirror site. The classic
> architecture - Nginx (serving static frontend, HTTPS, and caching) -> Apache
> (reverse proxy + CGI execution) -> cgit / git-http-backend - appears to be
> functional in principle.
> The clone failures with large Git repositories are likely caused by
> insufficient or inappropriate parameter configurations rather than the
> architecture itself.

Agreed, it is very likely that the transmission problem is caused by the
large size of the warehouse.

> P.S., I am the mentor of HUST OpenAtom Club, and our club is maintaining the
> hust mirror site.

Thanks very much.