RESOLVED WORKSFORME 242761
Cloning WebKit repo from Github frequently fails due to remote closing connection
https://bugs.webkit.org/show_bug.cgi?id=242761
Summary Cloning WebKit repo from Github frequently fails due to remote closing connec...
Ryosuke Niwa
Reported 2022-07-14 12:43:57 PDT
I keep seeing an issue here the remote closes connection receiving most of the content. e.g. % git clone git@github.com:WebKit/WebKit.git OpenSource Cloning into 'OpenSource'... remote: Enumerating objects: 4973318, done. remote: Counting objects: 100% (655/655), done. remote: Compressing objects: 100% (417/417), done. remote: Total 4973318 (delta 324), reused 474 (delta 231), pack-reused 4972663 Receiving objects: 100% (4973318/4973318), 8.33 GiB | 16.67 MiB/s, done. Connection to github.com closed by remote host. Resolving deltas: 100% (4067310/4067310), done.
Attachments
Ryosuke Niwa
Comment 1 2022-07-14 13:00:13 PDT
Looks like the third attempt finally worked.
Ryosuke Niwa
Comment 2 2022-07-14 13:03:19 PDT
Nope. It didn't :( Hitting the same issue: % git clone git@github.com:WebKit/WebKit.git OpenSource Cloning into 'OpenSource'... remote: Enumerating objects: 4973459, done. remote: Counting objects: 100% (20/20), done. remote: Compressing objects: 100% (19/19), done. remote: Total 4973459 (delta 1), reused 4 (delta 1), pack-reused 4973439 Receiving objects: 100% (4973459/4973459), 8.33 GiB | 17.50 MiB/s, done. Connection to github.com closed by remote host. Resolving deltas: 100% (4067636/4067636), done.
Alexey Proskuryakov
Comment 3 2022-07-14 13:04:05 PDT
Do we have some documentation that recommends git@github.com:WebKit/WebKit.git? I thought we suggested https://github.com/WebKit/WebKit.git.
Ryosuke Niwa
Comment 4 2022-07-14 13:07:12 PDT
(In reply to Alexey Proskuryakov from comment #3) > Do we have some documentation that recommends > git@github.com:WebKit/WebKit.git? I thought we suggested > https://github.com/WebKit/WebKit.git. Hm... so you think HTTPS is more stable?
Ryosuke Niwa
Comment 5 2022-07-14 13:47:13 PDT
Okay, so https worked. That's so odd! But I guess this is works-for-me.
Note You need to log in before you can comment on or make changes to this bug.