Jelmer Vernooij

I've now added a HTTPProxyUnauthorized exception as well. I'm not sure if Dulwich should get in the business of parsing WWW-Authenticate in this particular code path. One of the intentions...

For dulwich itself, yes - migrating to urllib3 was painful enough and I don't want to make library users go through that again. However, we could provide an abstract base...

reset should probably use a different call - build_index_from_tree is meant for fresh checkouts.

That would make sense for the porcelain module, at least; contributions in this area would certainly be welcome!

Sorry for the delay, I'll try to have another look at it this week.

Sorry, I'm currently traveling but will be able to take a look in a couple of days.

Can you reproduce the test failure with unittest?

The memory usage goes overboard in this line in _complete_thin_pack(): entries = list(indexer)

On Fri, Feb 15, 2019 at 09:10:04PM +0000, Matt wrote: > I'm seeing this behavior as well, even with small repositories. (~100 commits with around 10MB worth of data). According...

Dulwich has a LRUCache for recently read objects; you may be able to reduce the memory consumption by reducing the number of objects in the LRU Cache. See dulwich/pack.py