- Mar 09, 2013
-
-
Durham Goode authored
When running 'hg pull --rebase', I was seeing this exception 100% of the time as the python process was closing down: Exception TypeError: TypeError("'NoneType' object is not callable",) in <bound method Popen.__del__ of <subprocess.Popen object at 0x937c10>> ignored By storing the subprocess on the sshpeer, the subprocess seems to clean up correctly, and I no longer see the exception. I have no idea why this actually works, but I get a 0% repro if I store the subprocess in self.subprocess, and a 100% repro if I store None in self.subprocess. Possibly related to issue 2240.
-
- Feb 28, 2013
-
-
Durham Goode authored
When running commands like 'hg export -o mypatch-%N.patch', the blackbox would throw an exception because it tried to format %N. This change prevents it from trying to format the command string.
-
- Feb 09, 2013
-
-
Dan Villiom Podlaski Christiansen authored
avoid a couple of array copies and string interpolations
-
Dan Villiom Podlaski Christiansen authored
output table rows on distinct lines don't make the first row a table header
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
We mainly use them for option tables -- browsers bolding and centering them looks wrong.
-
- Feb 10, 2013
-
-
Dan Villiom Podlaski Christiansen authored
...for prettier HTML!
-
- Feb 09, 2013
-
-
Dan Villiom Podlaski Christiansen authored
It's generated from the raw ReST source, as returned from help.help_().
-
Dan Villiom Podlaski Christiansen authored
We move the logic for generating the unformatted ReST source to the help module, in order to eventually avoid calling commands.help_() from hgweb. No functionality change.
-
Dan Villiom Podlaski Christiansen authored
-
- Mar 01, 2013
-
-
Dan Villiom Podlaski Christiansen authored
-
Kevin Bullock authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- Feb 17, 2013
-
-
Matt Mackall authored
When we don't get an hgweb protocol response, we dump the response to the user for diagnostic purposes (it might be a cgitb message, for instance). But if we try to clone a bundle, we don't want to show the entire bundle in the error message. Also, we don't want fetch the full bundle multiple times during fallback. So we only fetch 1k here.
-
Matt Mackall authored
Pre-0.6c hgweb used text/plain for protocol responses. This meant that a web server could serve a static file and confuse a client into generating a nasty traceback. Now we insist that text/plain protocol responses not include a Content-Length, which older hgweb didn't generate but will typically be produced for static files.
-
- Feb 28, 2013
-
-
Bryan O'Sullivan authored
I often want to measure the cost of a function call before/after an optimization, where using top level "hg --time" timing introduces enough other noise that I can't tell if my efforts are having an effect. This decorator allows a developer to measure a function's cost with finer granularity.
-
Bryan O'Sullivan authored
This gives us a function we can reuse to count units of other kinds.
-
Thomas Arendsen Hein authored
The certificate was updated in March 2012. You can verify the certificate by using the Root CA certificate downloadable from https://ssl.intevation.de/ The intermediate CA is sent by https://hg.intevation.org/
-
- Feb 26, 2013
-
-
Mads Kiilerich authored
-
- Feb 28, 2013
-
-
Mads Kiilerich authored
The existence of these directories could not be relied on anyway and all dependencies on them should have been removed.
-
Mads Kiilerich authored
-
Mads Kiilerich authored
-
Mads Kiilerich authored
This makes a difference when working directory is dirty, especially when merging with a revision for which we don't have largefiles.
-
Mads Kiilerich authored
cachelfiles jumped through loops to handle merges and modified files ... but it did apparently no longer have a valid reason to do so. It should just always make sure that the largefiles referenced from the standins are present - no matter which actual largefile is stored in the working directory. If there is no standin then there is nothing to fetch. The old code usually verified the hash of all largefiles every time this function was invoked - for examply by 'update'. This change makes a trivial noop update 5-10 seconds faster on our repo (with the other 50% spent doing another unnecessary hashing of all largefiles).
-
Mads Kiilerich authored
Situations where a largefile for some reason wasn't available sometimes caused wrong largefile content and state. It has mostly been seen when interrupting download of largefiles ... and when introducing programming errors. Instead we now make sure to delete the old and wrong largefile. A missing file is a well-known error condition and much more reasonable way to handle the situation.
-
Mads Kiilerich authored
Largefiles can easily become missing - for example if it simply isn't available or the download fail. It might even be convenient to be able to work that way in some cases. But commiting missing largefiles as if they had been 'hg remove'd is plain wrong.
-
Mads Kiilerich authored
It might not have been created and it might have been removed.
-
Mads Kiilerich authored
Looking for a (potentially empty) directory was not reliable - both because it is a reasonable assumption that empty directories can be removed and because it wasn't created in all cases ... such as when pulling to an existing repository.
-
Mads Kiilerich authored
The test relied on the bug that 'pull largefiles from branchheads' didn't pull any largefiles from tip revision when it seemed like no largefiles had been checked out before.
-
Mads Kiilerich authored
The empty list was interpreted as all revisions - just like None is. The empty list is now handled explicitly.
-
Mads Kiilerich authored
Test output is changed in a case where one revision was pulled, but because of the off-by-one error it thought that 0 revisions were pulled ... and because of another bug it thus (tried to) fetch largefiles for all revisions. After this change it no longer reports failure when it failed while trying to fetch largefiles it shouldn't fetch. Largefiles that it shouldn't fetch but managed to fetch anyway will now correctly be missing later on. This change thus resolves some of unexplained test output introduced in 1e4eb1faba6e.
-
- Feb 23, 2013
-
-
Simon Heimberg authored
This lines were reported as unnecessary when running the tests on windows because the path was already printed with a slash and not a backslash.
-
Simon Heimberg authored
The test failed on windows before this patch.
-
- Feb 22, 2013
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-