upstream/mercurial-mirror Files · tests/test-manifestv2.t

sshpeer: initial definition and implementation of new SSH protocol...

sshpeer: initial definition and implementation of new SSH protocol The existing SSH protocol has several design flaws. Future commits will elaborate on these flaws as new features are introduced to combat these flaws. For now, hopefully you can take me for my word that a ground up rewrite of the SSH protocol is needed. This commit lays the foundation for a new SSH protocol by defining a mechanism to upgrade the SSH transport channel away from the default (version 1) protocol to something modern (which we'll call "version 2" for now). This upgrade process is detailed in the internals documentation for the wire protocol. The gist of it is the client sends a request line preceding the "hello" command/line which basically says "I'm requesting an upgrade: here's what I support." If the server recognizes that line, it processes the upgrade request and the transport channel is switched to use the new version of the protocol. If not, it sends an empty response, which is how all Mercurial SSH servers from the beginning of time reacted to unknown commands. The upgrade request is effectively ignored and the client continues to use the existing version of the protocol as if nothing happened. The new version of the SSH protocol is completely identical to version 1 aside from the upgrade dance and the bytes that follow. The immediate bytes that follow the protocol switch are defined to be a length framed "capabilities: " line containing the remote's advertised capabilities. In reality, this looks very similar to what the "hello" response would look like. But it will evolve quickly. The methodology by which the protocol will evolve is important. I'm not going to introduce the new protocol all at once. That would likely lead to endless bike shedding and forward progress would stall. Instead, I intend to tricle out new features and diversions from the existing protocol in small, incremental changes. To support the gradual evolution of the protocol, the on-the-wire advertised protocol name contains an "exp" to denote "experimental" and a 4 digit field to capture the sub-version of the protocol. Whenever we make a BC change to the wire protocol, we can increment this version and lock out all older clients because it will appear as a completely different protocol version. This means we can incur as many breaking changes as we want. We don't have to commit to supporting any one feature or idea for a long period of time. We can even evolve the handshake mechanism, because that is defined as being an implementation detail of the negotiated protocol version! Hopefully this lowers the barrier to accepting changes to the protocol and for experimenting with "radical" ideas during its development. In core, sshpeer received most of the attention. We haven't even implemented the server bits for the new protocol in core yet. Instead, we add very primitive support to our test server, mainly just to exercise the added code paths in sshpeer. Differential Revision: https://phab.mercurial-scm.org/D2061 # no-check-commit because of required foo_bar naming

Denis Laxalde - - Load All Authors

File last commit:

r34662:eb586ed5 default


                r35994:48a3a928

default

Download file

             test-manifestv2.t
        
                    102 lines
            
             | 2.4 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-manifestv2.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      Create repo with old manifest

        $ cat << EOF >> $HGRCPATH

        > [format]

        > usegeneraldelta=yes

        > EOF

        $ hg init existing

        $ cd existing

        $ echo footext > foo

        $ hg add foo

        $ hg commit -m initial

      We're using v1, so no manifestv2 entry is in requires yet.

        $ grep manifestv2 .hg/requires

        [1]

      Let's clone this with manifestv2 enabled to switch to the new format for

      future commits.

        $ cd ..

        $ hg clone --pull existing new --config experimental.manifestv2=1

        requesting all changes

        adding changesets

        adding manifests

        adding file changes

        added 1 changesets with 1 changes to 1 files

        new changesets 0fc9a4fafa44

        updating to branch default

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

        $ cd new

      Check that entry was added to .hg/requires.

        $ grep manifestv2 .hg/requires

        manifestv2

      Make a new commit.

        $ echo newfootext > foo

        $ hg commit -m new

      Check that the manifest actually switched to v2.

        $ hg debugdata -m 0

        foo\x0021e958b1dca695a60ee2e9cf151753204ee0f9e9 (esc)

        $ hg debugdata -m 1

        \x00 (esc)

        \x00foo\x00 (esc)

        I\xab\x7f\xb8(\x83\xcas\x15\x9d\xc2\xd3\xd3:5\x08\xbad5_ (esc)

      Check that manifestv2 is used if the requirement is present, even if it's

      disabled in the config.

        $ echo newerfootext > foo

        $ hg --config experimental.manifestv2=False commit -m newer

        $ hg debugdata -m 2

        \x00 (esc)

        \x00foo\x00 (esc)

        \xa6\xb1\xfb\xef]\x91\xa1\x19`\xf3.#\x90S\xf8\x06 \xe2\x19\x00 (esc)

      Check that we can still read v1 manifests.

        $ hg files -r 0

        foo

        $ cd ..

      Check that entry is added to .hg/requires on repo creation

        $ hg --config experimental.manifestv2=True init repo

        $ cd repo

        $ grep manifestv2 .hg/requires

        manifestv2

      Set up simple repo

        $ echo a > file1

        $ echo b > file2

        $ echo c > file3

        $ hg ci -Aqm 'initial'

        $ echo d > file2

        $ hg ci -m 'modify file2'

      Check that 'hg verify', which uses manifest.readdelta(), works

        $ hg verify

        checking changesets

        checking manifests

        crosschecking files in changesets and manifests

        checking files

        3 files, 2 changesets, 4 total revisions

      Check that manifest revlog is smaller than for v1

        $ hg debugindex -m

           rev    offset  length  delta linkrev nodeid       p1           p2

             0         0      81     -1       0 57361477c778 000000000000 000000000000

             1        81      33      0       1 aeaab5a2ef74 57361477c778 000000000000

	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

				Create repo with old manifest

				$ cat << EOF >> $HGRCPATH
				> [format]
				> usegeneraldelta=yes
				> EOF

				$ hg init existing
				$ cd existing
				$ echo footext > foo
				$ hg add foo
				$ hg commit -m initial

				We're using v1, so no manifestv2 entry is in requires yet.

				$ grep manifestv2 .hg/requires
				[1]

				Let's clone this with manifestv2 enabled to switch to the new format for
				future commits.

				$ cd ..
				$ hg clone --pull existing new --config experimental.manifestv2=1
				requesting all changes
				adding changesets
				adding manifests
				adding file changes
				added 1 changesets with 1 changes to 1 files
				new changesets 0fc9a4fafa44
				updating to branch default
				1 files updated, 0 files merged, 0 files removed, 0 files unresolved
				$ cd new

				Check that entry was added to .hg/requires.

				$ grep manifestv2 .hg/requires
				manifestv2

				Make a new commit.

				$ echo newfootext > foo
				$ hg commit -m new

				Check that the manifest actually switched to v2.

				$ hg debugdata -m 0
				foo\x0021e958b1dca695a60ee2e9cf151753204ee0f9e9 (esc)

				$ hg debugdata -m 1
				\x00 (esc)
				\x00foo\x00 (esc)
				I\xab\x7f\xb8(\x83\xcas\x15\x9d\xc2\xd3\xd3:5\x08\xbad5_ (esc)

				Check that manifestv2 is used if the requirement is present, even if it's
				disabled in the config.

				$ echo newerfootext > foo
				$ hg --config experimental.manifestv2=False commit -m newer

				$ hg debugdata -m 2
				\x00 (esc)
				\x00foo\x00 (esc)
				\xa6\xb1\xfb\xef]\x91\xa1\x19`\xf3.#\x90S\xf8\x06 \xe2\x19\x00 (esc)

				Check that we can still read v1 manifests.

				$ hg files -r 0
				foo

				$ cd ..

				Check that entry is added to .hg/requires on repo creation

				$ hg --config experimental.manifestv2=True init repo
				$ cd repo
				$ grep manifestv2 .hg/requires
				manifestv2

				Set up simple repo

				$ echo a > file1
				$ echo b > file2
				$ echo c > file3
				$ hg ci -Aqm 'initial'
				$ echo d > file2
				$ hg ci -m 'modify file2'

				Check that 'hg verify', which uses manifest.readdelta(), works

				$ hg verify
				checking changesets
				checking manifests
				crosschecking files in changesets and manifests
				checking files
				3 files, 2 changesets, 4 total revisions

				Check that manifest revlog is smaller than for v1

				$ hg debugindex -m
				rev offset length delta linkrev nodeid p1 p2
				0 0 81 -1 0 57361477c778 000000000000 000000000000
				1 81 33 0 1 aeaab5a2ef74 57361477c778 000000000000