- Jan 09, 2016
-
-
Yuya Nishihara authored
cmdutil.command wasn't a member of the registrar framework only for a historical reason. Let's make that happen. This patch keeps cmdutil.command as an alias for extension compatibility.
-
- May 15, 2017
-
-
Durham Goode authored
Commit 282b288aa20c removed the unused bundlecaps argument from the changegroup code. While it is unused in core Mercurial, it was an important feature for the remotefilelog extension because it allowed the exchange layer to communicate to the changegroup packer that this was a shallow repo and that filelogs should not be included. Without bundlecaps, there is currently no other way to pass that information along without a more extensive refactor of exchange, bundle, and changegroup code. This patch backs out the original removal, and merges it with some recent changes to changegroup apis.
-
- May 04, 2017
-
-
Pierre-Yves David authored
It is identical to 'getlocalchangegroup' with a shorter name.
-
- May 03, 2017
-
-
Martin von Zweigbergk authored
-
- Aug 09, 2016
-
-
Pierre-Yves David authored
We are to introduce more code constructing such object in the code base. It will be more convenient to pass a repository object, all current users already operate at the repository level anyway. More changes to the contructor argument are coming in later changeset.
-
- Aug 02, 2016
-
-
Pierre-Yves David authored
Bundle 2 is enable by default since 3.6 so we don't need this anymore. The remaining use of 'experimental.bundle2-exp' are there to test legacy behavior with bundle 1. Future patches will introduce a way outside of experimental to test that.
-
- Jul 17, 2016
-
-
Gregory Szorc authored
`hg debugbundle` is calling repr() on bundle2 part params, which are now util.sortdict instances. Unfortunately, repr() doesn't appear to be deterministic for util.sortdict. So, we implement one. We include the type name because that's the common convention for __repr__ implementations. Having the type name in `hg debugbundle` is a bit ugly. But it's a debug command and I don't care enough to fix it.
-
- Mar 15, 2016
-
-
Jun Wu authored
Some tests fail while running with chg because they do not flush their output streams. chgserver will make sure ui.flush is called after dispatch, but not after {ui,repo}setup. For other non-ui streams, it should be explicitly flushed since the request handler will use os._exit. This patch adds explicit flushes in test-bundle2-format.t, test-extension.t and test-obsolete.t. It will fix most test cases of them when running with chg.
-
- Feb 25, 2016
-
-
Pierre-Yves David authored
Now that bundle2 is used by default for all exchanges, this comment is obviously out of date. Having deep testing of the API and expected behavior of the format and its processing is still valuable, so the comment is updated.
-
- Dec 24, 2015
-
-
Bryan O'Sullivan authored
PyPy has looser semantics than CPython for when a generator's close method will be called. Forcing the gc causes it to be called at the right moment.
-
- Oct 16, 2015
-
-
Pierre-Yves David authored
This bundle command is meant to generate a bundle1, we enforce that to avoid test's misbehavior when moving to general-delta by default.
-
- Oct 08, 2015
-
-
Pierre-Yves David authored
The home of 'Abort' is 'error' not 'util' however, a lot of code seems to be confused about that and gives all the credit to 'util' instead of the hardworking 'error'. In a spirit of equity, we break the cycle of injustice and give back to 'error' the respect it deserves. And screw that 'util' poser. For great justice.
-
- Oct 05, 2015
-
-
Pierre-Yves David authored
We were reading the wrong key...
-
- Sep 30, 2015
-
-
Matt Mackall authored
-
- Sep 25, 2015
-
-
Pierre-Yves David authored
This introduce a test for the feature and fix the exception name that is different on default.
-
- Sep 29, 2015
-
-
Matt Mackall authored
Forgot to amend.
-
- Sep 23, 2015
-
-
Pierre-Yves David authored
This changeset adds support for a 'compression' parameter in bundle2 streams. When set, it controls the compression algorithm used for the payload part of the bundle2. There is currently no usage of this except in tests.
-
- Sep 28, 2015
-
-
Pierre-Yves David authored
Thanks to Greg Szorc for pointing this out.
-
- Sep 01, 2015
-
-
Augie Fackler authored
GeneratorExit means the other end of the conversation has already stopped listening, so don't try and yield out error information. Instead, just let the GeneratorExit propagate normally. This should resolve esoteric issues observed with servers that have aggressive timeouts waiting for data to send to clients logging internal Python errors[0]. This has been observed with both gunicorn's gevent worker model and with scm-manager's built-in webserver (which itself is something sitting inside jetty.) 0: Exception RuntimeError: 'generator ignored GeneratorExit' in <generator object getchunks at 0x7fd2f6c586e0> ignored
-
- Jun 10, 2015
-
-
Matt Harbison authored
This is a backout of 46727fea7a00, and a partial backout of c3ecbf694904. Windows won't execute 'dummyssh' directly, presumably because CreateProcess() doesn't know how to execute a bash script: $ hg clone -e "dummyssh" ssh://user@dummy/cloned sshclone remote: 'dummyssh' is not recognized as an internal or external command, remote: operable program or batch file. abort: no suitable response from remote hg! [255] With the restoration of python as the executable, $TESTDIR needs to be restored for these invocations, because python won't search $PATH for 'dummyssh': $ hg clone -e "python dummyssh" ssh://user@dummy/cloned sshclone remote: python: can't open file 'dummyssh': [Errno 2] No such file or directory abort: no suitable response from remote hg! [255]
-
- Jun 08, 2015
-
-
Matt Mackall authored
dummyssh is marked executable and is in the path, no need for python, TESTDIR, or quotes.
-
- May 27, 2015
-
-
Pierre-Yves David authored
The old output is very verbose and unsuitable for general debug level. It is however very useful for debugging bundle2 generation or consumption issues. All this verbose ouput is hidden under a 'devel.bundle2.debug' flag.
-
Pierre-Yves David authored
If we are about to hide the detailed debug output, we need some generic debug message to replace it in a concise way.
-
Pierre-Yves David authored
If we are about to hide the detailed debug output, we need some generic debug message to replace it.
-
Pierre-Yves David authored
If we are about to hide the detailed debug output, we need some generic debug message to replace it in a concise way.
-
Pierre-Yves David authored
If we are about to hide the detailed debug output, we need some generic debug message to replace it in a concise way.
-
Pierre-Yves David authored
If we are about to hide the detailed debug output, we need some generic debug message to replace it in a concise way.
-
Pierre-Yves David authored
If we are about to hide the detailed debug output, we need some generic debug message to replace it in a more compact way.
-
Pierre-Yves David authored
The part generation process was lacking a ui object and could not produce debug output. It seems valuable to have some debug output on this part too, especially now that we are planning to be able to hide it in the default --debug output.
-
Pierre-Yves David authored
This make the origin of the message more explicit.
-
Pierre-Yves David authored
This makes the origin of the message more explicit.
-
- May 10, 2015
-
-
Pierre-Yves David authored
When the progress extension is not enabled, each call to 'ui.progress' used to issue a debug message. This results is a very verbose output and often redundant in tests. Dropping it makes tests less volatile to factor they do not meant to test. We had to alter the sed trick in 'test-rename-merge2.t'. Sed is used to drop all output from a certain point and hidding the progress output remove its anchor. So we anchor on something else.
-
- Apr 09, 2015
-
-
Pierre-Yves David authored
It is finally time to freeze the bundle2 format! To do so we: - rename HG2Y to HG20, - drop "b2x:" prefix from all part names, - rename capability to "bundle2-exp" to "bundle2" - rename the hook flag from 'bundle2-exp' to 'bundle2'
-
- Apr 06, 2015
-
-
Pierre-Yves David authored
To support multiple bundle2 formats, we will need a function returning the proper unbundler according to the header. We introduce such aa function and change the usage in the code base. The function will get smarter in later changesets. This is somewhat similar to the dispatching we do for 'HG10' and 'HG11'. The main target is to allow HG2Y support in an extension to ease transition of companies using the experimental protocol in production (yeah...) But I've no doubt this will be useful when playing with a future HG21.
-
- Jan 15, 2015
-
-
Eric Sumner authored
This adds support for bundle2 files to the unbundle command.
-
Eric Sumner authored
This enables debugbundle to print supporting info for bundle2 files.
-
- Dec 17, 2014
-
-
Eric Sumner authored
Since the capitalization no longer carries any meaning (previous diff), this patch normalizes all of the bundle2 part type strings to lower case.
-
- Dec 18, 2014
-
-
Eric Sumner authored
This makes all bundle2 parts mandatory unless they are expressly made advisory via the keyword parameter or the bundlepart.mandatory property.
-
- Apr 17, 2014
-
-
Mads Kiilerich authored
-
Mads Kiilerich authored
-