- Jun 24, 2024
-
-
Jörg Sonnenberger authored
Current Illumos and older Solaris require _XOPEN_SOURCE for msg_control. O_DIRECTORY doesn't exist on older systems either, so fallback to O_RDONLY. It's good enough as a repository will require both R and X permission anyway.
-
- Jul 03, 2024
-
-
Pierre-Yves David authored
Cf `is_mmap_safe` docstring.
-
Pierre-Yves David authored
This fix the same kind of issue as 85d96517e650
-
Pierre-Yves David authored
Cf `is_mmap_safe` docstring.
-
Pierre-Yves David authored
Cf `is_mmap_safe` docstring.
-
Pierre-Yves David authored
This will be useful to safeguard mmap usage to void SIGBUS when repositories lives on a NFS drive.
-
- Jun 24, 2024
-
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
Since this format is still experimental, we don't want to have to side-step the `branch3` name in case people do start using it before it's stable.
-
Jörg Sonnenberger authored
Drop duplicate assignment from a merge failure. Save one loop iteration by exploiting that pendingnodes will be seennodes after the first round anyway, so just pre-initialize the set accordingly. From Anton Shestakov's review on !867. Performance difference for my test case is in the noise.
-
- Jun 11, 2024
-
-
Jörg Sonnenberger authored
Find the candidates for nodes with relevant markers by going over all markers instead of iterating over all nodes. Most nodes will not have markers anyway. Further optimize the code by allowing revsets as well, which reduces the materialization cost.
-
- Jun 13, 2024
-
-
Pierre-Yves David authored
If we go over 10 seconds, the number of white space changes.
-
- Jun 12, 2024
-
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Pierre-Yves David authored
We move the name back to the expected name of `changelog.i.a`.
-
Pierre-Yves David authored
Since a93e52f0b6ff we no longer use inline-revlog for the changelog. The goal there was to solve the lack of testing for the two variants (inline vs split) and reduce the complexity of the interaction with "diverted-write" on the changelog level. However many existing repository still have inline-changelog and we automatically move them to normal revlog as soon as we have the chances. Unfortunately This conversion is buggy and can result in the destruction of the changelog.i if hook triggers the "write pending" mechanism. The bugs comes from the "revlog splitting" logic and the "write_pending" logic stepping over each other. Ironically the change in a93e52f0b6ff aims at no longer having this kind of problem. This changesets fix this issue and add associated tests. Fixing this reveal that the transaction hooks end up not seeing the pending transaction content, because the name is not right ("changelog.i.s.a" instead of "changelog.i.s") we fix this in the next changeset.
-
- Jun 11, 2024
-
-
Pierre-Yves David authored
Before this patch, running `hg push -B book` to push the `book` bookmark sideway at the same time as a commit making it moving forward might result in the removal of the bookmark remotely. After this changeset, the push can still be raced, but to remove deletion happens. This is progress.
-
Pierre-Yves David authored
This is useful for testing.
-
Pierre-Yves David authored
The previous code was taking locks before entering with statements, so exception before the with statement would not release the lock (except for garbage collection). We need to move to a try except here because the logic is more complicated.
-
Pierre-Yves David authored
The previous code was taking locks before entering with statements, so exception before the with statement would not release the lock (except for garbage collection).
-
- Sep 06, 2023
-
-
Pierre-Yves David authored
This new tests show that the linkrev computed and sent by the server might end up being wrong during a widen operation.
-
- Jun 10, 2024
-
-
Jörg Sonnenberger authored
This makes it at least somewhat clearer that hg is talking about some specific feature and not just outdated code.
-
Pierre-Yves David authored
-
Raphaël Gomès authored
This was making the tests flaky after the recent patch¹ that opened up more of the code to the Rust-augmented status. [1] 865efc020c33
-
- May 23, 2024
-
-
Julien Cristau authored
This seems to have been removed in 6.5 (likely by 60f9602b413e).
-
- May 07, 2024
-
-
Anton Shestakov authored
We have an experimental config histedit.later-commits-first from c820866c52f9, and when it's true, the order of commits in histedit UI is reversed, both in text mode and in curses mode. But before this patch key presses in curses mode would change histedit actions in the same old order, i.e. trying to edit the latest commit (which would be first now) would put "edit" action on the last commit in the list. This wasn't a cosmetic issue, histedit would actually proceed to edit the first commit in the list. Let's map rules to display items (hopefully now correctly).
-
- Apr 26, 2024
-
-
Arseniy Alekseyev authored
This whitelist is too permissive because it allows matchers that contain disallowed ones deep inside, for example through `intersectionmatcher`. It is also too restrictive because it doesn't pass through some of the matchers we support, such as `patternmatcher`. It's also unnecessary because unsupported matchers raise `FallbackError` and we fall back anyway. Making this change makes more of the tests use rust code path, and therefore subtly change behavior. For example, rust status in largefiles repos seems to have strange behavior.
-
Arseniy Alekseyev authored
This is useful if we are to use it outside of Rust, when deciding whether or not to do some fast-path operation with a given matcher.
-
Arseniy Alekseyev authored
These happened to slip through the cracks earlier because they weren't caught by tests. Now that we're enabling rust fast path more widely these start breaking.
-
- May 06, 2024
-
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
- Apr 22, 2024
-
-
Georges Racinet authored
The need comes from the fact that `AncestorsIterator` and many Graph-related algorithms take ownership of the `Graph` they work with. This, in turn is due to them needing to accept the `Index` instances that are provided by the Python layers (that neither rhg nor `RHGitaly` use, of course): the fact that nowadays the Python layer holds an object that is itself implemented in Rust does not change the core problem that they cannot be tracked by the borrow checker. Even though it looks like cloning `Changelog` would be cheap, it seems hard to guarantee that on the long run. The object is already too rich for us to be comfortable with it, when using references is the most natural and guaranteed way of proceeding. The added test seems a bit superfleous, but it will act as a reminder that this feature is really useful until something in the Mercurial code base actually uses it.
-
- May 06, 2024
-
-
Raphaël Gomès authored
In case we do get a dirstate error, we want to get the full error message and not just an opaque `Dirstate error`.
-
Raphaël Gomès authored
More explanations in the previous changeset.
-