I see. Thanks for the help! Let me have a change in my bisect script to change everything.
Thx, Haochen From: Jonathan Wakely <[email protected]> Sent: Monday, January 5, 2026 5:45 AM On Sun, 4 Jan 2026, 11:54 Mark Wielaard, <[email protected]<mailto:[email protected]>> wrote: Hi Haochen, On Sun, Jan 04, 2026 at 02:45:17AM +0000, Jiang, Haochen via Gcc wrote: > Recently I got an issue on git fetch via https, seems starting from 12/23 or > around, > blocking my bisect script for a while. > [...] > I have also tried on other machines still similar. > > Is there anything strict applied to git clone via https leading to this issue? Yes, AI scraper bots again :{ See https://inbox.sourceware.org/[email protected] and notices posted at https://fosstodon.org/@sourceware We switched off the "smart protocol" for http(s) and enabled the "dumb protocol". The dumb git protocol works, but is somewhat inefficient and for really big repos like gcc.git requires thousands of fetches (and if you start fresh any failure like you reported will result in you having to start from scratch again). The git:// or ssh:// protocols still use the smart protocol and so should be more realiable. The mirrors on https://forge.sourceware.org/gcc/gcc-mirror and https://git.sr.ht/~sourceware/gcc are up to date and could also be used. It seems to bots have lost interest so maybe we can reduce the anubis paranoia and re-enable the smart protocol again. I'll try, but if the bots return we might have to disable it again, so using different protocol or a mirror if you have to use https might be a good idea for now. Maybe we should update the web page about git access to advise against fetching over https, since it's slow and inefficient (and might not work at all). The download pages request people to use mirrors to reduce load on the main server, it makes sense to give similar advice for obtaining the sources over git. We could give clear instructions for fetching from a different source and then switching the remote to point to gcc.gnu.org<http://gcc.gnu.org> after the initial fetch.
