Thu, 17 Sep 2015 07:33:44 -0400 i18n-it: include translation of DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:33:44 -0400] rev 26254
i18n-it: include translation of DEPRECATED
Thu, 17 Sep 2015 07:32:28 -0400 i18n-da: include translation of DEPRECATED
timeless@mozdev.org [Thu, 17 Sep 2015 07:32:28 -0400] rev 26253
i18n-da: include translation of DEPRECATED
Thu, 17 Sep 2015 07:31:07 -0400 test-i18n: always run non gettext tests
timeless@mozdev.org [Thu, 17 Sep 2015 07:31:07 -0400] rev 26252
test-i18n: always run non gettext tests
Tue, 15 Sep 2015 00:32:39 +0900 localrepo: refresh filecache stats only if transaction finished successfully
Yuya Nishihara <yuya@tcha.org> [Tue, 15 Sep 2015 00:32:39 +0900] rev 26251
localrepo: refresh filecache stats only if transaction finished successfully If commit is aborted by pretxncommit hook, in-memory changelog and manifest have entries that would be added. So they must be discarded on invalidate(). But the mechanism introduced by a710936c3037 doesn't handle this case well. It tries to mitigate the penalty of invalidate() by marking in-memory cache as "clean" on unlock assuming that they are identical to the stored data. But this assumption is wrong if stored data are rolled back by tr.abort(). This patch moves the hook to post-close action so that it will never be triggered on abort. This bug was originally reported to thg, which is only reproducible in command-server process on unix, evolve disabled. https://bitbucket.org/tortoisehg/thg/issues/4285/
Tue, 15 Sep 2015 21:00:28 +0900 localrepo: move closure of lock release to class
Yuya Nishihara <yuya@tcha.org> [Tue, 15 Sep 2015 21:00:28 +0900] rev 26250
localrepo: move closure of lock release to class It only captures "self", so it isn't necessary to be created dynamically.
Wed, 16 Sep 2015 22:30:36 +0800 highlight: add highlightfiles config option which takes a fileset (issue3005)
Anton Shestakov <av6@dwimlabs.net> [Wed, 16 Sep 2015 22:30:36 +0800] rev 26249
highlight: add highlightfiles config option which takes a fileset (issue3005) Highlight extension lacked a way to limit files by size, by extension, and/or by any other part of file path. A good solution would be to use a fileset, since it can check file path, extension and size (and more) in one expression. So this change introduces such an option, highlighfiles, which takes a fileset and on each request decides if the requested file should be highlighted. The default "size('<5M')" is, in a way, suggested in issue3005. checkfctx() limits the amount of work to just one file (subset kwarg in fileset.matchctx()). Monkey-patching works around issue4568, otherwise using filesets here while running hgweb in directory mode would say, for example, "Abort: **.py not under root", but this fix is very local and probably far from ideal. I suspect there to be a way to fix this for the whole hgweb and resolve the issue, but I don't know how to do it.
Fri, 04 Sep 2015 11:15:02 -0400 posix: shellquote do not require quoting for "+" (issue4818)
timeless@mozdev.org [Fri, 04 Sep 2015 11:15:02 -0400] rev 26248
posix: shellquote do not require quoting for "+" (issue4818)
Sat, 12 Sep 2015 12:16:39 -0700 hgweb: consume generator inside context manager (issue4756)
Gregory Szorc <gregory.szorc@gmail.com> [Sat, 12 Sep 2015 12:16:39 -0700] rev 26247
hgweb: consume generator inside context manager (issue4756) If code inside a context manager returns a generator, the context manager exits before the generator is iterated. hgweb was using a context manager to control thread safe access to a localrepository instance. But it was returning a generator, so there was a race condition between a previous request streaming a response to the client and a new request obtaining the released but in use repository. By iterating the generator inside the context manager, we ensure we don't release the repo instance until after the response has finished. With this change, hgweb finally appears to have full localrepository isolation between threads. I can no longer reproduce the 2 exceptions reported in issue4756. test-hgweb-non-interactive.t has been modified to consume the output of calling into a WSGI application. Without this, execution of the WSGI application stalls because of the added yield statement.
Thu, 27 Aug 2015 14:46:26 -0400 histedit: use one editor when multiple folds happen in a row (issue3524) (BC)
Augie Fackler <augie@google.com> [Thu, 27 Aug 2015 14:46:26 -0400] rev 26246
histedit: use one editor when multiple folds happen in a row (issue3524) (BC) This was the first ever feature request for histedit, originally filed back on April 4, 2009. Finally fixed. In the future we'll probably want to make it possible for other preprocessing steps to be added to the list, but for now we're skipping that because it's unclear what the API should look like without a proposed consumer.
Mon, 14 Sep 2015 18:41:09 +0800 hgweb: replace .sourcelast with .bottomline that does the same
Anton Shestakov <av6@dwimlabs.net> [Mon, 14 Sep 2015 18:41:09 +0800] rev 26245
hgweb: replace .sourcelast with .bottomline that does the same In paper and Coal, basically, div.sourcelast was only used to make a 1px border on the bottom of file source view (and only there). It's better to use bottomline class, that also exists for the same purpose (visually), but is used more widely and works without needing an empty <div>.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip