Jelmer Vernooij

On Mon, Nov 12, 2018 at 12:51:27AM -0800, Christian Ulrich wrote: > nginx has this in its logs > > ``` > 2018/11/12 09:31:24 [error] 16565#16565: *3177 upstream timed out...

it seems like a useful convention to copy, as alternative to e.g. restful proprietary APIs provided by GitHub/GitLab for creating pull requests.

What do other sites, e.g. GitHub, do in this case?

Thanks, I'll have a look. These are both operations that scale with the length of history per file.

Yeah, I think we'd want a cache rather than actually reading the repositories every time. Perhaps we could make FancyRepo a wrapper for dulwich.Repo rather than being derived from it?

On Thu, Jul 04, 2019 at 12:59:51AM -0700, Jonas Haag wrote: > Curious: Do you actually have that kind of use case with 1000+ repos? Yeah, I'm working on a...

I've worked around this for now by adding an app that just shows a single repository (a list of 10k repositories is not very usable anyway...) and loads that repository...

FWIW I really like this change too - and +1 for using /-/, since that's consistent with GitLab. Redirects for the old URLs would indeed be good.

Which version of Dulwich are you using? There have been some fixes recently that improve the strategy for delta resolution - significantly improving memory usage on certain kinds of repository.

FWIW a number of memory improvements have gone into Dulwich' server gode recently.