[PATCH 3 of 4 flagprocessor v8] revlog: flag processor
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Mon Jan 9 10:25:41 EST 2017
On 01/08/2017 10:42 PM, Gregory Szorc wrote:
> On Thu, Jan 5, 2017 at 9:42 AM, Remi Chaintron <remi at fb.com
> <mailto:remi at fb.com>> wrote:
>
> # HG changeset patch
> # User Remi Chaintron <remi at fb.com <mailto:remi at fb.com>>
> # Date 1483636648 0
> # Thu Jan 05 17:17:28 2017 +0000
> # Node ID 8701df1c04340e9951481dc4c366ba550b4e790f
> # Parent a93b1ff78332f4f78e77ec9aaa2c63f7f975399c
> revlog: flag processor
>
> Add the ability for revlog objects to process revision flags and apply
> registered transforms on read/write operations.
>
> This patch introduces:
> - the 'revlog._processflags()' method that looks at revision flags
> and applies
> flag processors registered on them. Due to the need to handle
> non-commutative
> operations, flag transforms are applied in stable order but the
> order in which
> the transforms are applied is reversed between read and write
> operations.
> - the 'addflagprocessor()' method allowing to register processors on
> flags.
> Flag processors are defined as a 3-tuple of (read, write, raw)
> functions to be
> applied depending on the operation being performed.
> - an update on 'revlog.addrevision()' behavior. The current
> flagprocessor design
> relies on extensions to wrap around 'addrevision()' to set flags
> on revision
> data, and on the flagprocessor to perform the actual
> transformation of its
> contents. In the lfs case, this means we need to process flags
> before we meet
> the 2GB size check, leading to performing some operations before
> it happens:
> - if flags are set on the revision data, we assume some extensions
> might be
> modifying the contents using the flag processor next, and we
> compute the
> node for the original revision data (still allowing extension to
> override
> the node by wrapping around 'addrevision()').
> - we then invoke the flag processor to apply registered transforms
> (in lfs's
> case, drastically reducing the size of large blobs).
> - finally, we proceed with the 2GB size check.
>
> Note: In the case a cachedelta is passed to 'addrevision()' and we
> detect the
> flag processor modified the revision data, we chose to trust the
> flag processor
> and drop the cachedelta.
>
>
> I've only been casually following this series, so apologies if my
> feedback below has been addressed already.
>
> From an architecture perspective, I really like this series.
>
> But one thing that is rubbing me the wrong way is the reserved USR
> flags.
Actually, these USR flag have been dropped of the official and are now
used in the tests. (so not part of BC). The test should probably use
explicit name to make this clearer.
The official approach regarding new flags is for people with new flag
usecase to "quickly" contact upstream to reserve one of the available
flag. Upstream do need to have actual support but act as a central
registry for flags meaning.
Rémi said he will follow up with some internal documentation about that.
(note, if someone want to make as case for USR flag, he can do it
independently once the case series is in)
> I like the idea of reserving flags for future use. However, for
> features that aren't in core, a simple bit is not sufficient to identify
> behavior. For example, extension "fbext" authored by Facebook and
> extension "mozext" authored by Mozilla could both use USR0 for different
> things. If someone at Facebook running "fbext" clones a Mozilla-hosted
> repo, their USR0 processor will do a completely different thing from
> what "mozext" intended. Chaos ensues.
>
> There are a number of ways to solve problems like this. One way is a
> central registry of transforms. But we only have 4 bits so that won't
> scale. Another is to use strings, probably with prefixes to "namespace"
> extensions. But we don't have an easy way to inject strings into
> revisions (although we could use a bit flag to indicate additional flags
> are at the beginning of the revlog chunk data in string format, kinda
> like how filelogs store copy/rename metadata). Another idea is repo
> requirements. You could add a requirement like "revlogusr0=fbext" to
> indicate that the USR0 flag is associated with "fbext." That way if
> another loaded extension providing USR0 is present, the repo will fail
> to open.
>
> But even the repo requirements solution has problems. What about `hg
> clone`? The remote server isn't advertising what the USR flags are
> doing. So, a client will happily start receiving changegroup data with
> flags having behavior defined by another extension. When they go to
> actually read that revision, things blow up. So for repos relying on USR
> flags, we need the client and/or server to advertise which USR flags
> they support and for what purpose and to fail fast if support isn't
> present. This means that a repo needs to know what USR flags are in use.
> This could be implemented as a repo requirement.
>
> I think it is fine to reserve a few bits for user flags. But we need the
> docs to indicate that repos relying on these flags are (currently) very
> fragile outside of tightly controlled environments and should not be
> used lightly.
>
> There are a few minor nits inline. None require a v9 unless you are
> already writing one IMO.
>
>
>
> diff --git a/mercurial/bundlerepo.py b/mercurial/bundlerepo.py
> --- a/mercurial/bundlerepo.py
> +++ b/mercurial/bundlerepo.py
> @@ -148,7 +148,10 @@
> delta = self._chunk(chain.pop())
> text = mdiff.patches(text, [delta])
>
> - self.checkhash(text, node, rev=rev)
> + text, validatehash = self._processflags(text, self.flags(rev),
> + 'read', raw=raw)
> + if validatehash:
> + self.checkhash(text, node, rev=rev)
> self._cache = (node, rev, text)
> return text
>
> diff --git a/mercurial/revlog.py b/mercurial/revlog.py
> --- a/mercurial/revlog.py
> +++ b/mercurial/revlog.py
> @@ -56,6 +56,10 @@
> REVIDX_ISCENSORED = (1 << 15) # revision has censor metadata, must
> be verified
> REVIDX_DEFAULT_FLAGS = 0
> REVIDX_KNOWN_FLAGS = REVIDX_ISCENSORED
> +# stable order in which flags need to be processed and their
> processors applied
> +REVIDX_FLAGS_ORDER = [
> + REVIDX_ISCENSORED,
> +]
very minor nits: manually defining REVIDX_KNOWN_FLAGS and
REVIDX_FLAGS_ORDER is "redundant". We could use:
REVIDX_KNOWN_FLAGS = reduce(lambda x,y: x|y, REVIDX_FLAGS_ORDER)
That would avoid silly mistake when updating one but not the other.
>
> # max size of revlog with inline data
> _maxinline = 131072
> @@ -64,6 +68,39 @@
> RevlogError = error.RevlogError
> LookupError = error.LookupError
> CensoredNodeError = error.CensoredNodeError
> +ProgrammingError = error.ProgrammingError
> +
> +# Store flag processors (cf. 'addflagprocessor()' to register)
> +_flagprocessors = { }
Should be {} (no space)
> +
> +def addflagprocessor(flag, processor):
> + """Register a flag processor on a revision data flag.
> +
> + Invariant:
> + - Flags need to be defined in REVIDX_KNOWN_FLAGS and
> REVIDX_FLAGS_ORDER.
> + - Only one flag processor can be registered on a specific flag.
> + - flagprocessors must be 3-tuples of functions (read, write,
> raw) with the
> + following signatures:
> + - (read) f(self, text) -> newtext, bool
> + - (write) f(self, text) -> newtext, bool
> + - (raw) f(self, text) -> bool
> + The boolean returned by these transforms is used to determine
> whether
> + 'newtext' can be used for hash integrity checking.
> +
> + Note: The 'raw' transform is used for changegroup generation
> and in some
> + debug commands. In this case the transform only indicates
> whether the
> + contents can be used for hash integrity checks.
> + """
> + if not flag & REVIDX_KNOWN_FLAGS:
> + raise ProgrammingError(_(
> + "cannot register processor on unknown flag '%x'." %
> (flag)))
small nits: you can assign a temporary 'msg' variable with your string
to avoid the function call overflow. We do this in multiple places.
> + if flag not in REVIDX_FLAGS_ORDER:
> + raise ProgrammingError(_(
> + "flag '%x' undefined in REVIDX_FLAGS_ORDER." % (flag)))
> + if flag in _flagprocessors:
> + raise error.Abort(_(
> + "cannot register multiple processors on flag '%x'." %
> (flag)))
> + _flagprocessors[flag] = processor
>
> def getoffset(q):
> return int(q >> 16)
> @@ -1231,11 +1268,6 @@
> if rev is None:
> rev = self.rev(node)
>
> - # check rev flags
> - if self.flags(rev) & ~REVIDX_KNOWN_FLAGS:
> - raise RevlogError(_('incompatible revision flag %x') %
> - (self.flags(rev) & ~REVIDX_KNOWN_FLAGS))
> -
> chain, stopped = self._deltachain(rev, stoprev=cachedrev)
> if stopped:
> text = self._cache[2]
> @@ -1249,7 +1281,12 @@
> bins = bins[1:]
>
> text = mdiff.patches(text, bins)
> - self.checkhash(text, node, rev=rev)
> +
> + text, validatehash = self._processflags(text,
> self.flags(rev), 'read',
> + raw=raw)
> + if validatehash:
> + self.checkhash(text, node, rev=rev)
> +
> self._cache = (node, rev, text)
> return text
>
> @@ -1261,6 +1298,58 @@
> """
> return hash(text, p1, p2)
>
> + def _processflags(self, text, flags, operation, raw=False):
> + """Inspect revision data flags and applies transforms
> defined by
> + registered flag processors.
> +
> + ``text`` - the revision data to process
> + ``flags`` - the revision flags
> + ``operation`` - the operation being performed (read of write)
>
>
> typo: "of"
>
>
> + ``raw`` - an optional argument describing if the raw transform should be
> + applied.
> +
> + This method processes the flags in the order (or reverse order if
> + ``operation`` is 'write') defined by REVIDX_FLAGS_ORDER, applying the
> + flag processors registered for present flags. The order of flags defined
> + in REVIDX_FLAGS_ORDER needs to be stable to allow non-commutativity.
> +
> + Returns a 2-tuple of ``(text, validatehash)`` where ``text`` is the
> + processed text and ``validatehash`` is a bool indicating whether the
> + returned text should be checked for hash integrity.
> +
> + Note: If the ``raw`` argument is set, it has precedence over the
> + operation and will only update the value of ``validatehash``.
> + """
> + if not operation in ['read', 'write']:
>
>
> Nit: tuples should be used for this pattern.
+1
> + raise ProgrammingError(_("invalid operation '%s'") % (operation))
> + # Check all flags are known.
> + if flags & ~REVIDX_KNOWN_FLAGS:
> + raise RevlogError(_("incompatible revision flag '%x'") %
> + (flags & ~REVIDX_KNOWN_FLAGS))
> + validatehash = True
> + # Depending on the operation (read or write), the order might be
> + # reversed due to non-commutative transforms.
> + orderedflags = REVIDX_FLAGS_ORDER
> + if operation == 'write':
> + orderedflags = reversed(orderedflags)
> +
> + for flag in orderedflags:
> + # If a flagprocessor has been registered for a known flag, apply the
> + # related operation transform and update result tuple.
> + if flag & flags:
> + vhash = True
> + processor = _flagprocessors.get(flag, None)
In another email, you said you forget a None check here.
We should probably push things a bit further. 'None' as a do nothing,
value seems fine (and we should probably test it). But I think we should
distinguish between None being explicitly set and the lack of value.
That would mean aborting if we encounter a flag that is known
(registered in known flag) but without any known way to handle it.
In your LFS case, this means that if the EXTSTORED flag is set on a
revision but no processors are registered for EXTSTORED we would
explicitly crash here. With a crash about a lacking way to handle flag
X, "easily" searchable for the user. Otherwise we would silently lets
the EXTSTORED carry one and later crash at a hash checking step.
In theory such case would not happens because LFS repo would be protect
with a lfs requirement and wire/disk exchange would be protected by the
correct capability but I would rather have a second line of defense here.
> +
> + if raw:
> + vhash = processor[2](self, text)
> + elif operation == 'read':
> + text, vhash = processor[0](self, text)
> + else: # write operation
> + text, vhash = processor[1](self, text)
> + validatehash = validatehash and vhash
> +
> + return text, validatehash
> +
> def checkhash(self, text, node, p1=None, p2=None, rev=None):
> """Check node hash integrity.
>
> @@ -1345,6 +1434,15 @@
> raise RevlogError(_("attempted to add linkrev -1 to %s")
> % self.indexfile)
>
> + if flags:
> + node = node or self.hash(text, p1, p2)
> +
> + newtext, validatehash = self._processflags(text, flags,
> 'write')
> +
> + if newtext != text and cachedelta is not None:
> + cachedelta = None
>
>
> You can drop the "cachedelta is not None" check because it doesn't
> matter. I think this reads better when the condition is simpler.
May it would be useful to issue a debug message here, to note a possible
inefficiency
> + text = newtext
> +
> if len(text) > _maxentrysize:
> raise RevlogError(
> _("%s: size of %d bytes exceeds maximum revlog
> storage of 2GiB")
> @@ -1354,10 +1452,14 @@
> if node in self.nodemap:
> return node
>
> + if validatehash:
> + self.checkhash(text, node, p1=p1, p2=p2)
> +
> dfh = None
> if not self._inline:
> dfh = self.opener(self.datafile, "a+")
> ifh = self.opener(self.indexfile, "a+",
> checkambig=self._checkambig)
> +
gratuitous new line introduction,
> try:
> return self._addrevision(node, text, transaction, link,
> p1, p2,
> flags, cachedelta, ifh, dfh)
> @@ -1423,7 +1525,7 @@
> - text is optional (can be None); if not set, cachedelta
> must be set.
> if both are set, they must correspond to each other.
> - raw is optional; if set to True, it indicates the
> revision data is to
> - be treated by processflags() as raw. It is usually set by
> changegroup
> + be treated by _processflags() as raw. It is usually set
Minor nits, that hunk should be in patch 1.
> by changegroup
> generation and debug commands.
> """
> btext = [text]
> @@ -1448,7 +1550,11 @@
> btext[0] = mdiff.patch(basetext, delta)
>
> try:
> - self.checkhash(btext[0], node, p1=p1, p2=p2)
> + btext[0], validatehash = self._processflags(btext[0],
> + flags, 'read',
> + raw=raw)
minor nits: could he useful to use temporary variable for the result to
avoid the line size issue on the method call.
> + if validatehash:
> + self.checkhash(btext[0], node, p1=p1, p2=p2)
> if flags & REVIDX_ISCENSORED:
> raise RevlogError(_('node %s is not censored')
> % node)
> except CensoredNodeError:
> diff --git a/tests/base64ext.py b/tests/base64ext.py
> new file mode 100644
> --- /dev/null
> +++ b/tests/base64ext.py
As discussed on IRC, I think we should gather everything in a
"revlogflagtest.py" extension (pick you prefered name), having 4
different extensions is not bringing much value and make things more
noisy than they could.
> @@ -0,0 +1,42 @@
> +# coding=UTF-8
> +
> +from __future__ import absolute_import
> +
> +import base64
> +
> +from mercurial import (
> + extensions,
> + filelog,
> + revlog,
> +)
> +
> +import flagprocessorsetup
This is not too important since we are about to merge them. But the
canonical way to another extension "module" object is through
mercurial.extensions.
> +
> +def bypass(self, text):
> + return False
> +
> +def encode(self, text):
> + return (base64.b64encode(text), False)
> +
> +def decode(self, text):
> + return (base64.b64decode(text), True)
> +
> +def addrevision(orig, self, text, transaction, link, p1, p2,
> cachedelta=None,
> + node=None, flags=revlog.REVIDX_DEFAULT_FLAGS):
> + if '[BASE64]' in text:
> + flags |= flagprocessorsetup.REVIDX_USR1
> + return orig(self, text, transaction, link, p1, p2,
> cachedelta=cachedelta,
> + node=node, flags=flags)
> +
> +def extsetup(ui):
> + wrapfunction = extensions.wrapfunction
> + wrapfunction(filelog.filelog, 'addrevision', addrevision)
> +
> + revlog.addflagprocessor(
> + flagprocessorsetup.REVIDX_USR1,
> + (
> + decode,
> + encode,
> + bypass,
> + ),
> + )
> diff --git a/tests/flagprocessorsetup.py b/tests/flagprocessorsetup.py
> new file mode 100644
> --- /dev/null
> +++ b/tests/flagprocessorsetup.py
> @@ -0,0 +1,43 @@
> +# coding=UTF-8
> +
> +from __future__ import absolute_import
> +
> +import base64
> +
> +from mercurial import (
> + changegroup,
> + extensions,
> + revlog,
> +)
> +
> +REVIDX_USR0 = (1 << 3)
> +REVIDX_USR1 = (1 << 2)
> +REVIDX_USR2 = (1 << 1)
> +REVIDX_USR3 = 1
As said earlier in this review, we should probably use more explicit
name here, eg: GZIP, BASE64 and NOOP.
In addition. having a large comment just before these definition about
how this is not the canonical way to do this would also be nice.
> +def supportedoutgoingversions(orig, repo):
> + versions = orig(repo)
> + versions.discard('01')
> + versions.discard('02')
> + versions.add('03')
> + return versions
> +
> +def allsupportedversions(orig, ui):
> + versions = orig(ui)
> + versions.add('03')
> + return versions
> +
> +def extsetup(ui):
> + # Enable changegroup3 for flags to be sent over the wire
> + wrapfunction = extensions.wrapfunction
> + wrapfunction(changegroup,
> + 'supportedoutgoingversions',
> + supportedoutgoingversions)
> + wrapfunction(changegroup,
> + 'allsupportedversions',
> + allsupportedversions)
> +
> + # Test only: add new flags for test extensions to use
> + testflags = [REVIDX_USR0, REVIDX_USR1, REVIDX_USR2, REVIDX_USR3]
> + revlog.REVIDX_KNOWN_FLAGS |= reduce(lambda x, y: x | y, testflags)
> + revlog.REVIDX_FLAGS_ORDER.extend(testflags)
> diff --git a/tests/gzipext.py b/tests/gzipext.py
> new file mode 100644
>
>
> I think it's a bit confusing to be doing compression in the flags since
> we already have another convention for compressing revlog chunks. But
> since this is just for testing purposes (and strictly speaking the
> revision data itself is compressed, not the chunk in the revlog), this
> is probably fine.
Yeah, when I suggested using gzip in test my idea was more about
commiting a gzip archive and gunzipping it at storage time.
In addition, I was actually thinking about urlquoting as the second use
case (but yes, I wrote base64 down…) to have more human readable tests.
However this is all for testing purpose and IRC discussion with Remi
concluded that the current tests were properly testing the behavior so
we dont -need- to change them. I'm fine with proceeding as is (beside
the existing change request)
>
>
> --- /dev/null
> +++ b/tests/gzipext.py
> @@ -0,0 +1,42 @@
> +# coding=UTF-8
> +
> +from __future__ import absolute_import
> +
> +import zlib
> +
> +from mercurial import (
> + extensions,
> + filelog,
> + revlog,
> +)
> +
> +import flagprocessorsetup
> +
> +def bypass(self, text):
> + return False
> +
> +def compress(self, text):
> + return (zlib.compress(text), False)
> +
> +def decompress(self, text):
> + return (zlib.decompress(text), True)
> +
> +def addrevision(orig, self, text, transaction, link, p1, p2,
> cachedelta=None,
> + node=None, flags=revlog.REVIDX_DEFAULT_FLAGS):
> + if '[GZIP]' in text:
> + flags |= flagprocessorsetup.REVIDX_USR2
> + return orig(self, text, transaction, link, p1, p2,
> cachedelta=cachedelta,
> + node=node, flags=flags)
> +
> +def extsetup(ui):
> + wrapfunction = extensions.wrapfunction
> + wrapfunction(filelog.filelog, 'addrevision', addrevision)
> +
> + revlog.addflagprocessor(
> + flagprocessorsetup.REVIDX_USR2,
> + (
> + decompress,
> + compress,
> + bypass
> + )
> + )
> diff --git a/tests/nopext.py b/tests/nopext.py
> new file mode 100644
> --- /dev/null
> +++ b/tests/nopext.py
> @@ -0,0 +1,37 @@
> +# coding=UTF-8
> +
> +from __future__ import absolute_import
> +
> +from mercurial import (
> + extensions,
> + filelog,
> + revlog,
> +)
> +
> +import flagprocessorsetup
> +
> +def validatehash(self, text):
> + return True
> +
> +def donothing(self, text):
> + return (text, True)
> +
> +def addrevision(orig, self, text, transaction, link, p1, p2,
> cachedelta=None,
> + node=None, flags=revlog.REVIDX_DEFAULT_FLAGS):
> + if '[NOP]' in text:
> + flags |= flagprocessorsetup.REVIDX_USR0
> + return orig(self, text, transaction, link, p1, p2,
> cachedelta=cachedelta,
> + node=node, flags=flags)
> +
> +def extsetup(ui):
> + wrapfunction = extensions.wrapfunction
> + wrapfunction(filelog.filelog, 'addrevision', addrevision)
> +
> + revlog.addflagprocessor(
> + flagprocessorsetup.REVIDX_USR0,
> + (
> + donothing,
> + donothing,
> + validatehash,
> + )
> + )
> diff --git a/tests/test-flagprocessor.t b/tests/test-flagprocessor.t
> new file mode 100644
> --- /dev/null
> +++ b/tests/test-flagprocessor.t
> @@ -0,0 +1,176 @@
> + $ hg init server
> + $ cd server
> + $ cat >> .hg/hgrc << EOF
> + > [extensions]
> + > flagprocessorsetup=$TESTDIR/flagprocessorsetup.py
> + > nop=$TESTDIR/nopext.py
> + > base64=$TESTDIR/base64ext.py
> + > gzip=$TESTDIR/gzipext.py
> + > EOF
> + $ cd ../
> +
> +# Clone server and enable extensions
> + $ hg clone -q server client
> + $ cd client
> + $ cat >> .hg/hgrc << EOF
> + > [extensions]
> + > flagprocessorsetup=$TESTDIR/flagprocessorsetup.py
> + > nop=$TESTDIR/nopext.py
> + > base64=$TESTDIR/base64ext.py
> + > gzip=$TESTDIR/gzipext.py
> + > EOF
> +
> +# Commit file that will trigger the nop extension
> + $ echo '[NOP]' > nop
> + $ hg commit -Aqm "nop"
> +
> +# Commit file that will trigger the base64 extension
> + $ echo '[BASE64]' > base64
> + $ hg commit -Aqm 'base64'
> +
> +# Commit file that will trigger the gzip extension
> + $ echo '[GZIP]' > gzip
> + $ hg commit -Aqm 'gzip'
> +
> +# Commit file that will trigger nop and base64
> + $ echo '[NOP][BASE64]' > nop-base64
> + $ hg commit -Aqm 'nop+base64'
> +
> +# Commit file that will trigger nop and gzip
> + $ echo '[NOP][GZIP]' > nop-gzip
> + $ hg commit -Aqm 'nop+gzip'
> +
> +# Commit file that will trigger base64 and gzip
> + $ echo '[BASE64][GZIP]' > base64-gzip
> + $ hg commit -Aqm 'base64+gzip'
> +
> +# Commit file that will trigger base64, gzip and nop
> + $ echo '[BASE64][GZIP][NOP]' > base64-gzip-nop
> + $ hg commit -Aqm 'base64+gzip+nop'
> +
> +# TEST: ensure the revision data is consistent
> + $ hg cat nop
> + [NOP]
> + $ hg debugdata nop 0
> + [NOP]
> +
> + $ hg cat -r . base64
> + [BASE64]
> + $ hg debugdata base64 0
> + W0JBU0U2NF0K (no-eol)
> +
> + $ hg cat -r . gzip
> + [GZIP]
> + $ hg debugdata gzip 0
> + x\x9c\x8bv\x8f\xf2\x0c\x88\xe5\x02\x00\x08\xc8\x01\xfd (no-eol) (esc)
> +
> + $ hg cat -r . nop-base64
> + [NOP][BASE64]
> + $ hg debugdata nop-base64 0
> + W05PUF1bQkFTRTY0XQo= (no-eol)
> +
> + $ hg cat -r . nop-gzip
> + [NOP][GZIP]
> + $ hg debugdata nop-gzip 0
> +
> x\x9c\x8b\xf6\xf3\x0f\x88\x8dv\x8f\xf2\x0c\x88\xe5\x02\x00\x199\x03\xa2
> (no-eol) (esc)
> +
> + $ hg cat -r . base64-gzip
> + [BASE64][GZIP]
> + $ hg debugdata base64-gzip 0
> + eJyLdnIMdjUziY12j/IMiOUCACLBBDo= (no-eol)
> +
> + $ hg cat -r . base64-gzip-nop
> + [BASE64][GZIP][NOP]
> + $ hg debugdata base64-gzip-nop 0
> + eJyLdnIMdjUziY12j/IMiI328w+I5QIAPj8F3w== (no-eol)
> +
> +# Push to the server
> + $ hg push
> + pushing to $TESTTMP/server
> + searching for changes
> + adding changesets
> + adding manifests
> + adding file changes
> + added 7 changesets with 7 changes to 7 files
> +
> +# Initialize new client (not cloning) and setup extension
> + $ cd ..
> + $ hg init client2
> + $ cd client2
> + $ cat >> .hg/hgrc << EOF
> + > [paths]
> + > default = $TESTTMP/server
> + > [extensions]
> + > flagprocessorsetup=$TESTDIR/flagprocessorsetup.py
> + > nop=$TESTDIR/nopext.py
> + > base64=$TESTDIR/base64ext.py
> + > gzip=$TESTDIR/gzipext.py
> + > EOF
> +
> +# Pull from server and update to latest revision
> + $ hg pull default
> + pulling from $TESTTMP/server
> + requesting all changes
> + adding changesets
> + adding manifests
> + adding file changes
> + added 7 changesets with 7 changes to 7 files
> + (run 'hg update' to get a working copy)
> + $ hg update
> + 7 files updated, 0 files merged, 0 files removed, 0 files unresolved
> +
> +# TEST: ensure the revision data is consistent
> + $ hg cat nop
> + [NOP]
> + $ hg debugdata nop 0
> + [NOP]
> +
> + $ hg cat -r . base64
> + [BASE64]
> + $ hg debugdata base64 0
> + W0JBU0U2NF0K (no-eol)
> +
> + $ hg cat -r . gzip
> + [GZIP]
> + $ hg debugdata gzip 0
> + x\x9c\x8bv\x8f\xf2\x0c\x88\xe5\x02\x00\x08\xc8\x01\xfd (no-eol) (esc)
> +
> + $ hg cat -r . nop-base64
> + [NOP][BASE64]
> + $ hg debugdata nop-base64 0
> + W05PUF1bQkFTRTY0XQo= (no-eol)
> +
> + $ hg cat -r . nop-gzip
> + [NOP][GZIP]
> + $ hg debugdata nop-gzip 0
> +
> x\x9c\x8b\xf6\xf3\x0f\x88\x8dv\x8f\xf2\x0c\x88\xe5\x02\x00\x199\x03\xa2
> (no-eol) (esc)
> +
> + $ hg cat -r . base64-gzip
> + [BASE64][GZIP]
> + $ hg debugdata base64-gzip 0
> + eJyLdnIMdjUziY12j/IMiOUCACLBBDo= (no-eol)
> +
> + $ hg cat -r . base64-gzip-nop
> + [BASE64][GZIP][NOP]
> + $ hg debugdata base64-gzip-nop 0
> + eJyLdnIMdjUziY12j/IMiI328w+I5QIAPj8F3w== (no-eol)
> +
> +# Create new client and enable extensions registering processors on
> the same flag
> + $ cd ../
> + $ hg init server2
> + $ cd server2
> + $ cat >> .hg/hgrc << EOF
> + > [extensions]
> + > flagprocessorsetup=$TESTDIR/flagprocessorsetup.py
> + > nop=$TESTDIR/nopext.py
> + > nop2=$TESTDIR/nopext.py
> + > EOF
> +
> +# TEST: ensure we cannot register several flag processors on the
> same flag
> + $ echo 'test' > file
> + $ hg commit -Aqm 'add file'
> + abort: cannot register multiple processors on flag '8'.
> + [255]
> +
> +
> +
--
Pierre-Yves David
More information about the Mercurial-devel
mailing list