Primer is hanging in typeshed's CI

[AlexWaygood]

See e.g. python/typeshed#11078

The issue is with a project in shard 0. I cancelled the shard after 25 minutes on the first run, and then re-ran it. I cancelled it after 15 minutes on the rerun.

[AlexWaygood]

The problematic project is zetta_utils. primer tries to run git clone --recurse-submodules https://github.com/ZettaAI/zetta_utils --depth 1. But if you run that currently, here's what happens:

>git clone --recurse-submodules https://github.com/ZettaAI/zetta_utils --depth 1
Cloning into 'zetta_utils'...
remote: Enumerating objects: 1212, done.
remote: Counting objects: 100% (1212/1212), done.
remote: Compressing objects: 100% (873/873), done.
remote: Total 1212 (delta 430), reused 830 (delta 291), pack-reused 0
Receiving objects: 100% (1212/1212), 574.33 KiB | 2.92 MiB/s, done.
Resolving deltas: 100% (430/430), done.
error: invalid path 'specs/sergiy/inference/cns/2_med/v3/9_old/\'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

I verified in AlexWaygood/typeshed#24 that primer works again if zetta_utils is excluded.

[AlexWaygood]

Looks like they might have added some "private submodules" or something, meaning that --recurse-submodules doesn't work for that repo anymore unless you're a member of the Zetta-AI team?? See ZettaAI/zetta_utils@9dd6a87

[AlexWaygood]

Should the project just be deleted from projects.py? Commented out for now? Should we change the way we try to clone the projects to avoid --recurse-submodules for some or all projects?

I await the opinions of mypy_primer maintainers :)

[hauntsaninja]

Thanks for investigating! I just removed it for now in d1263e0 , can figure out if we should change clone or something later

[AlexWaygood]

Thanks very much!