##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

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
FUJIWARA Katsunori - - Load All Authors

File last commit:

r30238:9843e3d9 stable
r35994:48a3a928 default
Show More
test-journal-share.t
153 lines | 4.5 KiB | text/troff | Tads3Lexer
/ tests / test-journal-share.t
History | Source | Raw |Copy content |Copy permalink
Martijn Pieters
journal: add share extension support...
 r29503 Journal extension test: tests the share extension support
$ cat >> testmocks.py << EOF
> # mock out util.getuser() and util.makedate() to supply testable values
> import os
> from mercurial import util
> def mockgetuser():
> return 'foobar'
>
> def mockmakedate():
> filename = os.path.join(os.environ['TESTTMP'], 'testtime')
> try:
> with open(filename, 'rb') as timef:
> time = float(timef.read()) + 1
> except IOError:
> time = 0.0
> with open(filename, 'wb') as timef:
> timef.write(str(time))
> return (time, 0)
>
> util.getuser = mockgetuser
> util.makedate = mockmakedate
> EOF
$ cat >> $HGRCPATH << EOF
> [extensions]
> journal=
> share=
> testmocks=`pwd`/testmocks.py
> [remotenames]
> rename.default=remote
> EOF
$ hg init repo
$ cd repo
$ hg bookmark bm
$ touch file0
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 $ hg commit -Am file0-added
Martijn Pieters
journal: add share extension support...
 r29503 adding file0
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 . commit -Am file0-added
0fd3805711f9 bm commit -Am file0-added
Martijn Pieters
journal: add share extension support...
 r29503
A shared working copy initially receives the same bookmarks and working copy
$ cd ..
$ hg share repo shared1
updating working directory
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ cd shared1
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 . share repo shared1
Martijn Pieters
journal: add share extension support...
 r29503
unless you explicitly share bookmarks
$ cd ..
$ hg share --bookmarks repo shared2
updating working directory
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ cd shared2
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 . share --bookmarks repo shared2
0fd3805711f9 bm commit -Am file0-added
Martijn Pieters
journal: add share extension support...
 r29503
Moving the bookmark in the original repository is only shown in the repository
that shares bookmarks
$ cd ../repo
$ touch file1
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 $ hg commit -Am file1-added
Martijn Pieters
journal: add share extension support...
 r29503 adding file1
$ cd ../shared1
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 . share repo shared1
Martijn Pieters
journal: add share extension support...
 r29503 $ cd ../shared2
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 4f354088b094 bm commit -Am file1-added
0fd3805711f9 . share --bookmarks repo shared2
0fd3805711f9 bm commit -Am file0-added
Martijn Pieters
journal: add share extension support...
 r29503
But working copy changes are always 'local'
$ cd ../repo
$ hg up 0
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
(leaving bookmark bm)
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 . up 0
4f354088b094 . commit -Am file1-added
4f354088b094 bm commit -Am file1-added
0fd3805711f9 . commit -Am file0-added
0fd3805711f9 bm commit -Am file0-added
Martijn Pieters
journal: add share extension support...
 r29503 $ cd ../shared2
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 4f354088b094 bm commit -Am file1-added
0fd3805711f9 . share --bookmarks repo shared2
0fd3805711f9 bm commit -Am file0-added
Martijn Pieters
journal: add share extension support...
 r29503 $ hg up tip
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg up 0
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
$ hg journal
previous locations of '.':
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 up 0
4f354088b094 up tip
0fd3805711f9 share --bookmarks repo shared2
Martijn Pieters
journal: add share extension support...
 r29503
Unsharing works as expected; the journal remains consistent
$ cd ../shared1
$ hg unshare
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 . share repo shared1
Martijn Pieters
journal: add share extension support...
 r29503 $ cd ../shared2
$ hg unshare
$ hg journal --all
previous locations of the working copy and bookmarks:
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 0fd3805711f9 . up 0
4f354088b094 . up tip
4f354088b094 bm commit -Am file1-added
0fd3805711f9 . share --bookmarks repo shared2
0fd3805711f9 bm commit -Am file0-added
Martijn Pieters
journal: add share extension support...
 r29503
New journal entries in the source repo no longer show up in the other working copies
$ cd ../repo
$ hg bookmark newbm -r tip
$ hg journal newbm
previous locations of 'newbm':
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 4f354088b094 bookmark newbm -r tip
Martijn Pieters
journal: add share extension support...
 r29503 $ cd ../shared2
$ hg journal newbm
previous locations of 'newbm':
no recorded locations
This applies for both directions
$ hg bookmark shared2bm -r tip
$ hg journal shared2bm
previous locations of 'shared2bm':
FUJIWARA Katsunori
tests: avoid quoting of commit messages for test portability...
 r30238 4f354088b094 bookmark shared2bm -r tip
Martijn Pieters
journal: add share extension support...
 r29503 $ cd ../repo
$ hg journal shared2bm
previous locations of 'shared2bm':
no recorded locations