Timeout with git clone

[Quentin Wenger]

Hi,

Thanks for the answers and comments.

> Yes, I agree that it probably would be much better to go back to use
> dulwich both for protocol serving and for providing data for the web
> frontend, instead of forking out to git. Disclaimer: I don't know has
> fast dulwich is these days. It could perhaps also be relevant to
> research what other python git hosting solutions do.

Are there other python git hosting solutions? The very reason I'm here is that I didn't really find anything else...

> If interested in contributing in this area, a first step could be to
> create a proof of concept of switching back to Dulwich and doing some
> benchmarks - both for local cloning with infinite network bandwidth
> (where I doubt dulwich can match pure git) and for more realistic remote
> internet bandwidth (where I guess it doesn't matter much).

Sounds like a good plan. I don't know if I'll find the time, but I'll try.

> But also note that subprocessio no longer only is used by pygrack. It is
> also used for run_git_command in
> kallithea/lib/vcs/backends/git/repository.py (introduced in
> 1f4d4b8d72f5), mainly for cloning and listing changesets. A full
> solution would require somehow replacing run_git_command with dulwich.
> But that can be done one at a time.

Yes I'm aware of that.

Kind regards,
Quentin