upstream/mercurial-mirror Files · tests/test-narrow-clone-non-narrow-server.t

wireprotov2: define and implement "manifestdata" command...

wireprotov2: define and implement "manifestdata" command The added command can be used for obtaining manifest data. Given a manifest path and set of manifest nodes, data about manifests can be retrieved. Unlike changeset data, we wish to emit deltas to describe manifest revisions. So the command uses the relatively new API for building delta requests and emitting them. The code calls into deltaparent(), which I'm not very keen of. There's still work to be done in delta generation land so implementation details of storage (e.g. exactly one delta is stored/available) don't creep into higher levels. But we can worry about this later (there is already a TODO on imanifestorage tracking this). On the subject of parent deltas, the server assumes parent revisions exist on the receiving end. This is obviously wrong for shallow clone. I've added TODOs to add a mechanism to the command to allow clients to specify desired behavior. This shouldn't be too difficult to implement. Another big change is that the client must explicitly request manifest nodes to retrieve. This is a major departure from "getbundle," where the server derives relevant manifests as it iterates changesets and sends them automatically. As implemented, the client must transmit each requested node to the server. At 20 bytes per node, we're looking at 2 MB per 100,000 nodes. Plus wire encoding overhead. This isn't ideal for clients with limited upload bandwidth. I plan to address this in the future by allowing alternate mechanisms for defining the revisions to retrieve. One idea is to define a range of changeset revisions whose manifest revisions to retrieve (similar to how "changesetdata" works). We almost certainly want an API to look up an individual manifest by node. And that's where I've chosen to start with the implementation. Again, a theme of this early exchangev2 work is I want to start by building primitives for accessing raw repository data first and see how far we can get with those before we need more complexity. Differential Revision: https://phab.mercurial-scm.org/D4488

Martin von Zweigbergk - - Load All Authors

File last commit:

r39566:576b9292 default


                r39673:c7a7c7e8

default

Download file

             test-narrow-clone-non-narrow-server.t
        
                    66 lines
            
             | 2.1 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-narrow-clone-non-narrow-server.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      Test attempting a narrow clone against a server that doesn't support narrowhg.

        $ . "$TESTDIR/narrow-library.sh"

        $ hg init master

        $ cd master

        $ for x in `$TESTDIR/seq.py 10`; do

        >   echo $x > "f$x"

        >   hg add "f$x"

        >   hg commit -m "Add $x"

        > done

        $ hg serve -a localhost -p $HGPORT1 --config extensions.narrow=! -d \

        >    --pid-file=hg.pid

        $ cat hg.pid >> "$DAEMON_PIDS"

        $ hg serve -a localhost -p $HGPORT2 -d --pid-file=hg.pid

        $ cat hg.pid >> "$DAEMON_PIDS"

      Verify that narrow is advertised in the bundle2 capabilities:

        $ cat >> unquote.py <<EOF

        > from __future__ import print_function

        > import sys

        > if sys.version[0] == '3':

        >     import urllib.parse as up

        >     unquote = up.unquote_plus

        > else:

        >     import urllib

        >     unquote = urllib.unquote_plus

        > print(unquote(list(sys.stdin)[1]))

        > EOF

        $ echo hello | hg -R . serve --stdio | \

        >   $PYTHON unquote.py | grep narrow

        narrow=v0

        rev-branch-cache changegroupsubset exp-narrow-1 getbundle known lookup protocaps pushkey streamreqs=generaldelta,revlogv1 unbundle=HG10GZ,HG10BZ,HG10UN unbundlehash

        $ cd ..

        $ hg clone --narrow --include f1 http://localhost:$HGPORT1/ narrowclone

        requesting all changes

        abort: server doesn't support narrow clones

        [255]

      Make a narrow clone (via HGPORT2), then try to narrow and widen

      into it (from HGPORT1) to prove that narrowing is fine and widening fails

      gracefully:

        $ hg clone -r 0 --narrow --include f1 http://localhost:$HGPORT2/ narrowclone

        adding changesets

        adding manifests

        adding file changes

        added 1 changesets with 1 changes to 1 files

        new changesets * (glob)

        updating to branch default

        1 files updated, 0 files merged, 0 files removed, 0 files unresolved

        $ cd narrowclone

        $ hg tracked --addexclude f2 http://localhost:$HGPORT1/

        comparing with http://localhost:$HGPORT1/

        searching for changes

        looking for local changes to affected paths

        $ hg tracked --addinclude f1 http://localhost:$HGPORT1/

        comparing with http://localhost:$HGPORT1/

        searching for changes

        no changes found

        abort: server doesn't support narrow clones

        [255]

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				Test attempting a narrow clone against a server that doesn't support narrowhg.

				$ . "$TESTDIR/narrow-library.sh"

				$ hg init master
				$ cd master

				$ for x in `$TESTDIR/seq.py 10`; do
				> echo $x > "f$x"
				> hg add "f$x"
				> hg commit -m "Add $x"
				> done

				$ hg serve -a localhost -p $HGPORT1 --config extensions.narrow=! -d \
				> --pid-file=hg.pid
				$ cat hg.pid >> "$DAEMON_PIDS"
				$ hg serve -a localhost -p $HGPORT2 -d --pid-file=hg.pid
				$ cat hg.pid >> "$DAEMON_PIDS"

				Verify that narrow is advertised in the bundle2 capabilities:

				$ cat >> unquote.py <<EOF
				> from __future__ import print_function
				> import sys
				> if sys.version[0] == '3':
				> import urllib.parse as up
				> unquote = up.unquote_plus
				> else:
				> import urllib
				> unquote = urllib.unquote_plus
				> print(unquote(list(sys.stdin)[1]))
				> EOF
				$ echo hello \| hg -R . serve --stdio \| \
				> $PYTHON unquote.py \| grep narrow
				narrow=v0
				rev-branch-cache changegroupsubset exp-narrow-1 getbundle known lookup protocaps pushkey streamreqs=generaldelta,revlogv1 unbundle=HG10GZ,HG10BZ,HG10UN unbundlehash

				$ cd ..

				$ hg clone --narrow --include f1 http://localhost:$HGPORT1/ narrowclone
				requesting all changes
				abort: server doesn't support narrow clones
				[255]

				Make a narrow clone (via HGPORT2), then try to narrow and widen
				into it (from HGPORT1) to prove that narrowing is fine and widening fails
				gracefully:
				$ hg clone -r 0 --narrow --include f1 http://localhost:$HGPORT2/ narrowclone
				adding changesets
				adding manifests
				adding file changes
				added 1 changesets with 1 changes to 1 files
				new changesets * (glob)
				updating to branch default
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved
				$ cd narrowclone
				$ hg tracked --addexclude f2 http://localhost:$HGPORT1/
				comparing with http://localhost:$HGPORT1/
				searching for changes
				looking for local changes to affected paths
				$ hg tracked --addinclude f1 http://localhost:$HGPORT1/
				comparing with http://localhost:$HGPORT1/
				searching for changes
				no changes found
				abort: server doesn't support narrow clones
				[255]