comparison mercurial/bundle2.py @ 21130:1ff06386217f

bundle2: introduce `replycaps` part for on-demand reply

The bundle2 processing does not create a bundle2 reply by default anymore.  It
is only done if the client requests it with a `replycaps` part. This part is
called `replycaps` as it will eventually contain data about which bundle2
capabilities are supported by the client.

We have to add a flag to the test command to control whether a reply is
generated or not.

21129:07bcbf326c8d

    before final usage.

    Unknown Mandatory part will abort the process.
    """
    op = bundleoperation(repo, transactiongetter)
    # todo:
    # - only create reply bundle if requested.
    op.reply = bundle20(op.ui)
    # todo:
    # - replace this is a init function soon.
    # - exception catching
    unbundler.params
    iterparts = unbundler.iterparts()

        heads.append(h)
        h = inpart.read(20)
    assert not h
    if heads != op.repo.heads():
        raise exchange.PushRaced()

21130:1ff06386217f

    before final usage.

    Unknown Mandatory part will abort the process.
    """
    op = bundleoperation(repo, transactiongetter)
    # todo:
    # - replace this is a init function soon.
    # - exception catching
    unbundler.params
    iterparts = unbundler.iterparts()

        heads.append(h)
        h = inpart.read(20)
    assert not h
    if heads != op.repo.heads():
        raise exchange.PushRaced()

@parthandler('replycaps')
def handlereplycaps(op, inpart):
    """Notify that a reply bundle should be created

    Will convey bundle capability at some point too."""
    if op.reply is None:
        op.reply = bundle20(op.ui)