Mercurial > hg
view relnotes/5.9 @ 50336:cf4d2f31660d stable
chg: populate CHGHG if not set
Normally, chg determines which `hg` executable to use by first consulting the
`$CHGHG` and `$HG` environment variables, and if neither are present defaults
to the `hg` found in the user's `$PATH`. If built with the `HGPATHREL` compiler
flag, chg will instead assume that there exists an `hg` executable in the same
directory as the `chg` binary and attempt to use that.
This can cause problems in situations where there are multiple actively-used
Mercurial installations on the same system. When a `chg` client connects to a
running command server, the server process performs some basic validation to
determine whether a new command server needs to be spawned. These checks include
things like checking certain "sensitive" environment variables and config
sections, as well as checking whether the mtime of the extensions, hg's
`__version__.py` module, and the Python interpreter have changed.
Crucially, the command server doesn't explicitly check whether the executable it
is running from matches the executable that the `chg` client would have
otherwise invoked had there been no existing command server process. Without
`HGPATHREL`, this still gets implicitly checked during the validation step,
because the only way to specify an alternate hg executable (apart from `$PATH`)
is via the `$CHGHG` and `$HG` environment variables, both of which are checked.
With `HGPATHREL`, however, the command server has no way of knowing which hg
executable the client would have run. This means that a client located at
`/version_B/bin/chg` will happily connect to a command server running
`/version_A/bin/hg` instead of `/version_B/bin/hg` as expected. A simple
solution is to have the client set `$CHGHG` itself, which then allows the
command server's environment validation to work as intended.
I have tested this manually using two locally built hg installations and it
seems to work with no ill effects. That said, I'm not sure how to write an
automated test for this since the `chg` available to the tests isn't even built
with the `HGPATHREL` compiler flag to begin with.
author | Arun Kulshreshtha <akulshreshtha@janestreet.com> |
---|---|
date | Mon, 27 Mar 2023 17:30:14 -0400 |
parents | 809e780c72e5 |
children |
line wrap: on
line source
== New Features == * `hg config` now has a `--source` option to show where each configuration value comes from. * Introduced a command (debug-repair-issue6528) to repair repositories affected by issue6528 where certain files would show up as modified even if they were clean due to an issue in the copy-tracing code. == Default Format Change == These changes affect newly created repositories (or new clone) done with Mercurial 5.9. == New Experimental Features == * A `changelogv2` format has been introduced. It is not ready for use yet, but will be used later to address some of the weaknesses of the current revlog format. * Initial experiment and support for `dirstatev2`, a new dirstate format that addresses some of the weaknesses of the current dirstate format. Python + C and Rust support are being implemented, but the Rust solution is the one currently getting the attention for performance. * Initial support for `rhg status`. `rhg` is the Rust wrapper executable for hg that shortcuts some commands for faster execution speed. == Bug Fixes == * Fixed committing empty files with `narrow` * Allow overriding `pip`'s pep517 compliance to build C or Rust extensions * Fixed regression on outgoing email when not specifying revisions * Fixed a regression causing bookmarks to disappear when using Rust persistent nodemap * Fixed a regression (in 5.9.1) introduced in 5.9 when cloning repos with deep filenames * Fixed detection of directories becoming symlinks, but only when using the Rust extensions. * Fixed ignore and include not composing in the Rust status * `hg commit --interactive` now handles deselecting edits of a rename * Fixed a case where `hg evolve` gives different results when interrupted * Fixed a memory leak in phases computation * `histedit` and `shelve` don't swallow errors when updating the working copy anymore * Improve error message when detecting content-divergence with a hidden common predecessor * No longer re-order parents in filelog, see issue6533 * Fix revisions affected by issue6533 on the fly during exchange * Many Windows fixes for stability and py3 compatibility improvements * Many other miscellaneous fixes == Backwards Compatibility Changes == == Internal API Changes == The Dirstate API have been updated as the previous function leaked some internal details and did not distinguish between two important cases: "We are changing parent and need to adjust the dirstate" and "some command is changing which file is tracked". To clarify the situation: * the following functions have been deprecated, - `dirstate.add`, - `dirstate.normal`, - `dirstate.normallookup`, - `dirstate.merge`, - `dirstate.otherparent`, - `dirstate.remove`, - `dirstate.drop`, - `dirstateitem.__getitem__`, * these new functions are added for the "adjusting parents" use-case: - `dirstate.update_file`, - `dirstate.update_file_p1`, * these new function are added for the "adjusting wc file" use-case": - `dirstate.set_tracked`, - `dirstate.set_untracked`, - `dirstate.set_clean`, - `dirstate.set_possibly_dirty`, See inline documentation of the new functions for details. * Additionally, the following have been deprecated: - `urlutil.getpath` function - `localrepository.updatecaches`' `full` argument * The following have been removed: - `revlog.revlogio` has been removed