- Dec 05, 2018
-
-
Martin von Zweigbergk authored
test-shelve.t dominated run time for all shelve tests. Before: # Ran 9 tests, 1 skipped, 0 failed. real 0m43.568s user 2m15.822s sys 0m40.857s After: # Ran 11 tests, 1 skipped, 0 failed. real 0m24.574s user 2m21.354s sys 0m40.435s Differential Revision: https://phab.mercurial-scm.org/D5388
-
Martin von Zweigbergk authored
The progress helper class keeps track of its current position, so we don't need a "count" variable for that. Differential Revision: https://phab.mercurial-scm.org/D5386
-
Martin von Zweigbergk authored
We had already given the initial value of "count[0]" a name, so just use that when applicable. Differential Revision: https://phab.mercurial-scm.org/D5385
-
Martin von Zweigbergk authored
Simpler is better. Differential Revision: https://phab.mercurial-scm.org/D5384
-
Martin von Zweigbergk authored
The "count" container is never used after this point, so there is no need to update it. Differential Revision: https://phab.mercurial-scm.org/D5383
-
Martin von Zweigbergk authored
The "count" variable is generally used for updating progress, but early in fileserverclient.request(), its used to mean the total count. We already have another "total" variable for that, so it seems much clearer to use that. Differential Revision: https://phab.mercurial-scm.org/D5382
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5381
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5380
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5379
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5378
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5377
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5376
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5375
-
- Dec 04, 2018
-
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5374
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5373
-
- Jul 13, 2018
-
-
Boris Feld authored
We rename "aggressivemergedelta" argument to "forceaggressivemergedelta". The previous argument naming could infer an absolute control on the behavior. However, the code show we respect the config option if set.
-
Boris Feld authored
The behavior was correct. Now it is correct and tested.
-
- Dec 05, 2018
-
-
Augie Fackler authored
This should fix the test on FreeBSD. Differential Revision: https://phab.mercurial-scm.org/D5387
-
- Dec 03, 2018
-
-
idlsoft authored
This extension should be helpful for feature branches - based workflows. At my company we first considered branches, but weren't sure about creating a lot of permanent objects. We tried bookmarks, but found some scenarios to be difficult to control. The main problem, was the active bookmark being moved on update. Disabling that made everything a lot more predictable. Bookmarks move on commit, and updating means switching between them. The extension also implements a few minor features to better guide the workflow: - hg bookmark NAME can be ambiguous (create or move), unlike hg branch. The extension requires -rev to move. - require an active bookmark on commit. - some bookmarks can be protected (like @), useful for teams, that require code reviews. - block creation of new branches. The initial implementation requires no changes in the core, but it does rely on some implementation details. I thought it may be useful to discuss the functionality first, and then focus making the code more robust. Differential Revision: https://phab.mercurial-scm.org/D4312
-
- Dec 04, 2018
-
-
Georges Racinet authored
This isn't the prettiest way of doing it, but it doesn't require looking up cargo, or wondering whether that should be part of setup.py clean. Differential Revision: https://phab.mercurial-scm.org/D5369
-
Georges Racinet authored
It was confusing to have p1 and parents.1 ; (p1, p2) is clearer. Differential Revision: https://phab.mercurial-scm.org/D5365
-
Augie Fackler authored
This is the same fix as 90e26ef4cbb1, just repeated on the new file location. Differential Revision: https://phab.mercurial-scm.org/D5371
-
Martin von Zweigbergk authored
The whole file is already guarded by "#require execbit". Differential Revision: https://phab.mercurial-scm.org/D5366
-
Martin von Zweigbergk authored
If you have an old obsolescence-chain of commits that has been pruned and you narrow your repo so that some of those commits get stripped (because they affected the removed paths), then we would currently resurrect the commit that came before (along the obsmarker chain) the last stripped commit. That happens by the usual rules for obsmarker-stripping. However, it's quite surprising when it happens when you narrow your repo. This patch makes narrowing not strip obsmarkers. Differential Revision: https://phab.mercurial-scm.org/D5364
-
- Nov 18, 2018
-
-
Yuya Nishihara authored
They were ui.debug() just because commandserver.log() was noop if no client connected.
-
Yuya Nishihara authored
The default rotating options are copied from the blackbox extension.
-
- Nov 10, 2018
-
-
Yuya Nishihara authored
This allows us to set the log path relative to $XDG_RUNTIME_DIR, for instance. [cmdserver] log = $XDG_RUNTIME_DIR/chg/server.log
-
Yuya Nishihara authored
The "pager subcommand" message is removed since ui isn't accessible there. I think that's okay as cmdtable[cmd]() will call attachio() and some debug message will be printed.
-
Yuya Nishihara authored
The global commandserver.log() will be replaced with this.
-
Yuya Nishihara authored
This allows us to keep track of server events before client connects to the server. Tests will be added later. Currently there's no log() call to check if things are working well.
-
Yuya Nishihara authored
Future patches will move the logging facility out of the server class, so cmdserver.log can't be (ab)used for this purpose. Instead, let's hook the factory function to raise exception.
-
- Nov 18, 2018
-
-
Yuya Nishihara authored
These classes will be used in command server. They are similar to the blackboxlogger, but it can't be factored out since the blackbox is so tightly coupled with a repo object.
-
- Dec 04, 2018
-
-
Augie Fackler authored
-
durin42 authored
-
durin42 authored
-
- Nov 20, 2018
-
-
Martin von Zweigbergk authored
Before this patch, when rebasing a file called "foo/bar", we would check e.g. if "/foo" (i.e. rooted at the file system root) was a symlink. Differential Revision: https://phab.mercurial-scm.org/D5361
-
- Dec 04, 2018
-
-
Martin von Zweigbergk authored
Thanks to Yuya for providing this test case in https://bz.mercurial-scm.org/show_bug.cgi?id=5818. Differential Revision: https://phab.mercurial-scm.org/D5368
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D5367
-
- Oct 28, 2018
-
-
Yuya Nishihara authored
index_get_parents() is an internal function, which doesn't check if the specified rev is valid. If rustlazyancestors() were instantiated with an invalid stoprev, it would access to invalid memory region. This is NOT a security fix as there's no Python code triggering the bug, but included in this series to not give a notion about the memory issue fixed by the previous patch.
-
- Nov 01, 2018
-
-
Yuya Nishihara authored
82d6a35cf432 wasn't enough. Several callers don't check negative revisions but for -1 (nullrev), which would directly lead to out-of-bounds read, and buffer overflow could follow. RCE might be doable with carefully crafted revlog structure, though I don't think this would be useful attack surface.
-