upstream/mercurial-mirror Files · tests/test-cat.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

Ryan McElroy - - Load All Authors

File last commit:

r35010:407ec7f3 default


                r35994:48a3a928

default

Download file

             test-cat.t
        
                    131 lines
            
             | 2.1 KiB
            
                | text/troff
            
             |
                Tads3Lexer
            
             / tests / test-cat.t
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

        $ hg init

        $ echo 0 > a

        $ echo 0 > b

        $ hg ci -A -m m

        adding a

        adding b

        $ hg rm a

        $ hg cat a

        0

        $ hg cat --decode a # more tests in test-encode

        0

        $ echo 1 > b

        $ hg ci -m m

        $ echo 2 > b

        $ hg cat -r 0 a

        0

        $ hg cat -r 0 b

        0

        $ hg cat -r 1 a

        a: no such file in rev 7040230c159c

        [1]

        $ hg cat -r 1 b

        1

      Test multiple files

        $ echo 3 > c

        $ hg ci -Am addmore c

        $ hg cat b c

        1

        3

        $ hg cat .

        1

        3

        $ hg cat . c

        1

        3

      Test fileset

        $ hg cat 'set:not(b) or a'

        3

        $ hg cat 'set:c or b'

        1

        3

        $ mkdir tmp

        $ hg cat --output tmp/HH_%H c

        $ hg cat --output tmp/RR_%R c

        $ hg cat --output tmp/h_%h c

        $ hg cat --output tmp/r_%r c

        $ hg cat --output tmp/%s_s c

        $ hg cat --output tmp/%d%%_d c

        $ hg cat --output tmp/%p_p c

        $ hg log -r . --template "{rev}: {node|short}\n"

        2: 45116003780e

        $ find tmp -type f | sort

        tmp/.%_d

        tmp/HH_45116003780e3678b333fb2c99fa7d559c8457e9

        tmp/RR_2

        tmp/c_p

        tmp/c_s

        tmp/h_45116003780e

        tmp/r_2

      Test template output

        $ hg --cwd tmp cat ../b ../c -T '== {path} ({abspath}) ==\n{data}'

        == ../b (b) ==

        1

        == ../c (c) ==

        3

        $ hg cat b c -Tjson --output -

        [

         {

          "abspath": "b",

          "data": "1\n",

          "path": "b"

         },

         {

          "abspath": "c",

          "data": "3\n",

          "path": "c"

         }

        ]

        $ hg cat b c -Tjson --output 'tmp/%p.json'

        $ cat tmp/b.json

        [

         {

          "abspath": "b",

          "data": "1\n",

          "path": "b"

         }

        ]

        $ cat tmp/c.json

        [

         {

          "abspath": "c",

          "data": "3\n",

          "path": "c"

         }

        ]

      Test working directory

        $ echo b-wdir > b

        $ hg cat -r 'wdir()' b

        b-wdir

      Environment variables are not visible by default

        $ PATTERN='t4' hg log -r '.' -T "{ifcontains('PATTERN', envvars, 'yes', 'no')}\n"

        no

      Environment variable visibility can be explicit

        $ PATTERN='t4' hg log -r '.' -T "{envvars % '{key} -> {value}\n'}" \

        >                 --config "experimental.exportableenviron=PATTERN"

        PATTERN -> t4

      Test behavior of output when directory structure does not already exist

        $ mkdir foo

        $ echo a > foo/a

        $ hg add foo/a

        $ hg commit -qm "add foo/a"

        $ hg cat --output "output/%p" foo/a

        $ cat output/foo/a

        a

	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

				$ hg init
				$ echo 0 > a
				$ echo 0 > b
				$ hg ci -A -m m
				adding a
				adding b
				$ hg rm a
				$ hg cat a
				0
				$ hg cat --decode a # more tests in test-encode
				0
				$ echo 1 > b
				$ hg ci -m m
				$ echo 2 > b
				$ hg cat -r 0 a
				0
				$ hg cat -r 0 b
				0
				$ hg cat -r 1 a
				a: no such file in rev 7040230c159c
				[1]
				$ hg cat -r 1 b
				1

				Test multiple files

				$ echo 3 > c
				$ hg ci -Am addmore c
				$ hg cat b c
				1
				3
				$ hg cat .
				1
				3
				$ hg cat . c
				1
				3

				Test fileset

				$ hg cat 'set:not(b) or a'
				3
				$ hg cat 'set:c or b'
				1
				3

				$ mkdir tmp
				$ hg cat --output tmp/HH_%H c
				$ hg cat --output tmp/RR_%R c
				$ hg cat --output tmp/h_%h c
				$ hg cat --output tmp/r_%r c
				$ hg cat --output tmp/%s_s c
				$ hg cat --output tmp/%d%%_d c
				$ hg cat --output tmp/%p_p c
				$ hg log -r . --template "{rev}: {node\|short}\n"
				2: 45116003780e
				$ find tmp -type f \| sort
				tmp/.%_d
				tmp/HH_45116003780e3678b333fb2c99fa7d559c8457e9
				tmp/RR_2
				tmp/c_p
				tmp/c_s
				tmp/h_45116003780e
				tmp/r_2

				Test template output

				$ hg --cwd tmp cat ../b ../c -T '== {path} ({abspath}) ==\n{data}'
				== ../b (b) ==
				1
				== ../c (c) ==
				3

				$ hg cat b c -Tjson --output -
				[
				{
				"abspath": "b",
				"data": "1\n",
				"path": "b"
				},
				{
				"abspath": "c",
				"data": "3\n",
				"path": "c"
				}
				]

				$ hg cat b c -Tjson --output 'tmp/%p.json'
				$ cat tmp/b.json
				[
				{
				"abspath": "b",
				"data": "1\n",
				"path": "b"
				}
				]
				$ cat tmp/c.json
				[
				{
				"abspath": "c",
				"data": "3\n",
				"path": "c"
				}
				]

				Test working directory

				$ echo b-wdir > b
				$ hg cat -r 'wdir()' b
				b-wdir

				Environment variables are not visible by default

				$ PATTERN='t4' hg log -r '.' -T "{ifcontains('PATTERN', envvars, 'yes', 'no')}\n"
				no

				Environment variable visibility can be explicit

				$ PATTERN='t4' hg log -r '.' -T "{envvars % '{key} -> {value}\n'}" \
				> --config "experimental.exportableenviron=PATTERN"
				PATTERN -> t4

				Test behavior of output when directory structure does not already exist

				$ mkdir foo
				$ echo a > foo/a
				$ hg add foo/a
				$ hg commit -qm "add foo/a"
				$ hg cat --output "output/%p" foo/a
				$ cat output/foo/a
				a