[PATCH 2 of 2] setdiscovery: stop limiting the number of local head we initially send

[Martin von Zweigbergk]

On Tue, Apr 16, 2019 at 8:59 PM Martin von Zweigbergk <martinvonz at google.com>
wrote:

>
>
> On Tue, Apr 16, 2019 at 11:41 AM Pierre-Yves David <
> pierre-yves.david at ens-lyon.org> wrote:
>
>> # HG changeset patch
>> # User Pierre-Yves David <pierre-yves.david at octobus.net>
>> # Date 1555428398 -7200
>> #      Tue Apr 16 17:26:38 2019 +0200
>> # Node ID ffaa98def33a903f132ec4177d36823a741b6ef6
>> # Parent  017778a4463a8e6ecb4b17cacf46a3ab27bdb239
>> # EXP-Topic discovery-speedup
>> # Available At https://bitbucket.org/octobus/mercurial-devel/
>> #              hg pull https://bitbucket.org/octobus/mercurial-devel/ -r
>> ffaa98def33a
>> setdiscovery: stop limiting the number of local head we initially send
>>
>
> I think I tried something like this before. I still have a commit in my
> repo. I don't remember why I didn't send it. Perhaps the issue was that the
> heads are sent in HTTP headers and we need to limit the size of those to
> work with restrictive proxies and servers?
>
>
By the way, if I'm right about that, it would be nice to have a devel
config that makes the server reject requests longer than a configured
length. Then we could set that to 2k or something in tests, so we can catch
this in tests in the future.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20190416/d7c1046c/attachment.html>