FR: Resolve many SSH issues by having networked `jj git` commands shell out to `git` #4979

arxanas · 2024-11-26T16:58:04Z

Update: Current status

This is now implemented and released in jj 0.26, but not yet the default. See https://jj-vcs.github.io/jj/latest/config/#git-subprocessing-behaviour. TLDR: jj config set --user git.subprocess=true.

Is your feature request related to a problem? Please describe.

Many jj git commands fail on less common setups, oftentimes because libgit2 doesn't support certain features (see additional context).

libgit2 itself uses libssh2 rather than OpenSSH, so it often doesn't behave the way that users would expect with their current git/ssh usage.

We've discussed having jj git commands literally shell out to git, rather than using the libgit2 implementation, most recently in #4937 (comment). I'm opening this issue to justify and track that proposal.

Describe the solution you'd like

Change jj git commands to execute git directly where appropriate.

This is not risk-free. For example, git-branchless does this and instead has issues like git sync --pull, git submit hang indefinitely when asking for password (arxanas/git-branchless#433) (note that it tries to run git in the background and communicate via stdin/stdout). But there are substantially fewer networking-related issues there, so it seems like a better default state of affairs for most users.

Describe alternatives you've considered

Continue using libgit2+libssh2: It seems like there's a significant number of issues caused by lack of support in libgit2, to the point that it impedes new and existing users, and we don't have the bandwidth or expertise to address them all.
Switch to Gitoxide: I don't think Gitoxide currently supports all of these workflows, and might not in the future. Gitoxide even shells out to git at present for certain use-cases (reading certain config?).

Additional context

Here's my enumeration of issues that might be resolved or resolveable by shelling out to Git. It would be nice if we could mostly solve them with a single mechanism!

SSH:

Clone/fetch/push/pull:

The text was updated successfully, but these errors were encountered:

gulbanana · 2024-12-26T10:06:11Z

It would certainly fix some issues. Do we have any concerns about inconsistency between git-backend ops performed by git itself and similar operations performed by jj's other commands?

arxanas · 2025-01-02T00:47:57Z

It would certainly fix some issues. Do we have any concerns about inconsistency between git-backend ops performed by git itself and similar operations performed by jj's other commands?

There are some existing issues, such as that some Git tooling doesn't handle commits with empty messages well. For that reason, jj git push checks and forbids pushing commits with empty messages. But I don't anticipate any new issues that would arise from using libgit2 vs git to push.

Reasoning: `jj` fails to push/fetch over ssh depending on the system. Issue jj-vcs#4979 lists over 20 related issues on this and proposes shelling out to `git` for tasks related to the network (in fact, just push/fetch are enough). This PR implements this. Implementation Details: This PR implements shelling out to `git` via `std::process::Command`. There are 2 sharp edges with the patch: - it relies on having to parse out git errors to match the error codes (and parsing git2's errors in one particular instance to match the error behaviour). This seems mostly unavoidable - it is using a new feature flag `shell` to switch on to shelling out. this doesn't seem the best approach, and it would be great to get some feedback on what would be best. A flag on jj git + adding it to the jj config seems to be a good enough idea Testing: Run the rust tests: ``` $ cargo test # checks we didn't screw up the baseline $ cargo test --features=shell # test the shelling out ``` Build with shell-out enabled: ``` $ cargo build --features=shell ``` Clone a private repo: ``` $ jj git clone <REPO_SSH_URL> ``` Create new commit and push ``` $ echo "TEST" > this_is_a_test_file.txt $ jj describe -m 'test commit' $ jj git push -b <branch> ```

arxanas · 2025-01-02T19:32:58Z

As a potential risk, @emilazy pointed this out on Discord:

another thing that probably needs consideration is packaging – getting git on PATH is no burden for macOS or Linux users, but I imagine we probably have prospective Windows users who don't want to install Git Bash or similar…?

So we should be sure to think about the workflow+UX for Windows users, or anyone else who doesn't happen to have git on their PATH for whatever reason.

I recall at least one situation where a Windows user was excited to use jj specifically because it didn't require git, and then were disappointed that something in their workflow actually did need git (maybe? I don't remember exactly what happened).
A compiled-to-WebAssembly distribution might not have git available, although in such a context, it seems likely that we wouldn't support pushing anyways.
There's some discussion in that Discord thread about Nix users, but I would assume for now that Nix users know how to handle it themselves.

emilazy · 2025-01-02T19:39:48Z

Just to record what I said on the Discord, I think that it’s basically no issue for anything but Windows, and for a seamless Windows experience we could build our own Git binaries in CI and ship them with Jujutsu (in the limit, by using build.rs fun to literally embed a stripped‐down Git main() in our jj.exe and shelling out to ourselves) – but I think this isn’t worth worrying about until we work on a polished Windows installation experience in general.

Reasoning: `jj` fails to push/fetch over ssh depending on the system. Issue jj-vcs#4979 lists over 20 related issues on this and proposes shelling out to `git` for tasks related to the network (in fact, just push/fetch are enough). This PR implements this. Users can either enable shelling out to git in a config file: ```toml [git] shell = true ``` Or via a CLI argument, e.g.: `jj git clone --shell <url>` Implementation Details: This PR implements shelling out to `git` via `std::process::Command`. There are 2 sharp edges with the patch: - it relies on having to parse out git errors to match the error codes (and parsing git2's errors in one particular instance to match the error behaviour). This seems mostly unavoidable - to ensure matching behaviour with git2, the tests are maintained across the two implementations. This is done using test_case, as with the rest of the codebase Testing: Run the rust tests: ``` $ cargo test ``` Build with shell-out enabled: ``` $ cargo build ``` Clone a private repo: ``` $ jj git clone --shell <REPO_SSH_URL> ``` Create new commit and push ``` $ echo "TEST" > this_is_a_test_file.txt $ jj describe -m 'test commit' $ jj git push --shell -b <branch> ```

gulbanana · 2025-01-03T13:49:34Z

I think "for git interop, install git so that jj can use it to connect to remotes" is reasonable for now, even on Windows. We could make it a little better by trying some hardcoded locations in case of installs that haven't set PATH.

Reasoning: `jj` fails to push/fetch over ssh depending on the system. Issue jj-vcs#4979 lists over 20 related issues on this and proposes spawning a `git` subprocess for tasks related to the network (in fact, just push/fetch are enough). This PR implements this. Users can either enable shelling out to git in a config file: ```toml [git] subprocess = true ``` Implementation Details: This PR implements shelling out to `git` via `std::process::Command`. There are 2 sharp edges with the patch: - it relies on having to parse out git errors to match the error codes (and parsing git2's errors in one particular instance to match the error behaviour). This seems mostly unavoidable - to ensure matching behaviour with git2, the tests are maintained across the two implementations. This is done using test_case, as with the rest of the codebase Testing: Run the rust tests: ``` $ cargo test ``` Build: ``` $ cargo build ``` Clone a private repo: ``` $ path/to/jj git clone --config='git.subprocess=true' <REPO_SSH_URL> ``` Create new commit and push ``` $ echo "TEST" > this_is_a_test_file.txt $ path/to/jj describe -m 'test commit' $ path/to/jj git push --config='git.subprocess=true' -b <branch> ```  Issues Closed With a grain of salt, but most of these problems should be fixed (or at least checked if they are fixed). They are the ones listed in jj-vcs#4979 . SSH: - jj-vcs#63 - jj-vcs#440 - jj-vcs#1455 - jj-vcs#1507 - jj-vcs#2931 - jj-vcs#2958 - jj-vcs#3322 - jj-vcs#4101 - jj-vcs#4333 - jj-vcs#4386 - jj-vcs#4488 - jj-vcs#4591 - jj-vcs#4802 - jj-vcs#4870 - jj-vcs#4937 - jj-vcs#4978 - jj-vcs#5120 - jj-vcs#5166 Clone/fetch/push/pull: - jj-vcs#360 - jj-vcs#1278 - jj-vcs#1957 - jj-vcs#2295 - jj-vcs#3851 - jj-vcs#4177 - jj-vcs#4682 - jj-vcs#4719 - jj-vcs#4889 - jj-vcs#5147 - jj-vcs#5238 Notable Holdouts: - Interactive HTTP authentication (jj-vcs#401, jj-vcs#469) - libssh2-sys dependency on windows problem (can only be removed if/when we get rid of libgit2): jj-vcs#3984

Reasoning: `jj` fails to push/fetch over ssh depending on the system. Issue jj-vcs#4979 lists over 20 related issues on this and proposes spawning a `git` subprocess for tasks related to the network (in fact, just push/fetch are enough). This PR implements this. Implementation Details: This PR implements shelling out to `git` via `std::process::Command`. There are 2 sharp edges with the patch: - it relies on having to parse out git errors to match the error codes (and parsing git2's errors in one particular instance to match the error behaviour). This seems mostly unavoidable - to ensure matching behaviour with git2, the tests are maintained across the two implementations. This is done using test_case, as with the rest of the codebase Testing: Run the rust tests: ``` $ cargo test ``` Build: ``` $ cargo build ``` Clone a private repo: ``` $ path/to/jj git clone --config='git.subprocess=true' <REPO_SSH_URL> ``` Create new commit and push ``` $ echo "TEST" > this_is_a_test_file.txt $ path/to/jj describe -m 'test commit' $ path/to/jj git push --config='git.subprocess=true' -b <branch> ``` Issues Closed With a grain of salt, but most of these problems should be fixed (or at least checked if they are fixed). They are the ones listed in jj-vcs#4979 . SSH: - jj-vcs#63 - jj-vcs#440 - jj-vcs#1455 - jj-vcs#1507 - jj-vcs#2931 - jj-vcs#2958 - jj-vcs#3322 - jj-vcs#4101 - jj-vcs#4333 - jj-vcs#4386 - jj-vcs#4488 - jj-vcs#4591 - jj-vcs#4802 - jj-vcs#4870 - jj-vcs#4937 - jj-vcs#4978 - jj-vcs#5120 - jj-vcs#5166 Clone/fetch/push/pull: - jj-vcs#360 - jj-vcs#1278 - jj-vcs#1957 - jj-vcs#2295 - jj-vcs#3851 - jj-vcs#4177 - jj-vcs#4682 - jj-vcs#4719 - jj-vcs#4889 - jj-vcs#5147 - jj-vcs#5238 Notable Holdouts: - Interactive HTTP authentication (jj-vcs#401, jj-vcs#469) - libssh2-sys dependency on windows problem (can only be removed if/when we get rid of libgit2): jj-vcs#3984

Reasoning: `jj` fails to push/fetch over ssh depending on the system. Issue #4979 lists over 20 related issues on this and proposes spawning a `git` subprocess for tasks related to the network (in fact, just push/fetch are enough). This PR implements this. Implementation Details: This PR implements shelling out to `git` via `std::process::Command`. There are 2 sharp edges with the patch: - it relies on having to parse out git errors to match the error codes (and parsing git2's errors in one particular instance to match the error behaviour). This seems mostly unavoidable - to ensure matching behaviour with git2, the tests are maintained across the two implementations. This is done using test_case, as with the rest of the codebase Testing: Run the rust tests: ``` $ cargo test ``` Build: ``` $ cargo build ``` Clone a private repo: ``` $ path/to/jj git clone --config='git.subprocess=true' <REPO_SSH_URL> ``` Create new commit and push ``` $ echo "TEST" > this_is_a_test_file.txt $ path/to/jj describe -m 'test commit' $ path/to/jj git push --config='git.subprocess=true' -b <branch> ``` Issues Closed With a grain of salt, but most of these problems should be fixed (or at least checked if they are fixed). They are the ones listed in #4979 . SSH: - #63 - #440 - #1455 - #1507 - #2931 - #2958 - #3322 - #4101 - #4333 - #4386 - #4488 - #4591 - #4802 - #4870 - #4937 - #4978 - #5120 - #5166 Clone/fetch/push/pull: - #360 - #1278 - #1957 - #2295 - #3851 - #4177 - #4682 - #4719 - #4889 - #5147 - #5238 Notable Holdouts: - Interactive HTTP authentication (#401, #469) - libssh2-sys dependency on windows problem (can only be removed if/when we get rid of libgit2): #3984

jdmarshall · 2025-01-24T22:13:49Z

There are some existing issues, such as that some Git tooling doesn't handle commits with empty messages well. For that reason, jj git push checks and forbids pushing commits with empty messages. But I don't anticipate any new issues that would arise from using libgit2 vs git to push.

As someone who subscribes to the theory that git commit -m is an antipattern, refusing empty commit messages out of hand makes me happy. That sounds like a feature, not a bug.

I would love it if jj users spent some of the time and frustration saved on wrangling frequent commits into writing better commit messages.

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [martinvonz/jj](https://github.com/martinvonz/jj) | minor | `v0.25.0` -> `v0.26.0` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>martinvonz/jj (martinvonz/jj)</summary> ### [`v0.26.0`](https://github.com/jj-vcs/jj/releases/tag/v0.26.0) [Compare Source](jj-vcs/jj@v0.25.0...v0.26.0) ##### About jj is a Git-compatible version control system that is both simple and powerful. See the [installation instructions](https://jj-vcs.github.io/jj/v0.26.0/install-and-setup/) to get started. ##### Release highlights - Improved Git push/fetch compatibility by spawning an external `git` process. This can be enabled by the `git.subprocess=true` config knob, and will be the default in a future release. - `jj log` can now show cryptographic commit signatures. The output can be controlled by the `ui.show-cryptographic-signatures=true` config knob. ##### Breaking changes - `jj abandon` now deletes bookmarks pointing to the revisions to be abandoned. Use `--retain-bookmarks` to move bookmarks backwards. If deleted bookmarks were tracking remote bookmarks, the associated bookmarks (or branches) will be deleted from the remote on `jj git push --all`. [#3505](jj-vcs/jj#3505) - `jj init --git` and `jj init --git-repo` have been removed. They were deprecated in early 2024. Use `jj git init` instead. - The following deprecated commands have been removed: - `jj cat` is replaced by `jj file show`. - `jj chmod` is replaced by `jj file chmod`. - `jj files` is replaced by `jj file list`. - The deprecated `-l` short alias for `--limit` in `jj log`, `jj op log` and `jj obslog` has been removed. The `-n` short alias can be used instead. - The deprecated `--siblings` options for `jj split` has been removed. `jj split --parallel` can be used instead. - The deprecated `fix.tool-command` config option has been removed. - In colocated repos, the Git index now contains the changes from all parents of the working copy instead of just the first parent (`HEAD`). 2-sided conflicts from the merged parents are now added to the Git index as conflicts as well. - The following change introduced in 0.25.0 is reverted: - `jj config list` now prints inline tables `{ key = value, .. }` literally. Inner items of inline tables are no longer merged across configuration files. - `jj resolve` will now attempt to resolve all conflicted files instead of resolving the first conflicted file. To resolve a single file, pass a file path to `jj resolve`. - `jj util mangen` is replaced with `jj util install-man-pages`, which can install man pages for all `jj` subcommands to a given path. - In `jj config list` template, `value` is now typed as `ConfigValue`, not as `String` serialized in TOML syntax. - `jj git remote add`/`set-url` now converts relative Git remote path to absolute path. - `jj log`/`op log` now applies `-n`/`--limit` *before* the items are reversed. Rationale: It's more useful to see the N most recent commits/operations, and is more performant. The old behavior can be achieved by `jj log .. | head`. [#5403](jj-vcs/jj#5403) - Upgraded `scm-record` from v0.4.0 to v0.5.0. See release notes at <https://github.com/arxanas/scm-record/releases/tag/v0.5.0>. - The builtin pager is switched to [streampager](https://github.com/markbt/streampager/). It can handle large inputs better and can be configured. - Conflicts materialized in the working copy before `jj 0.19.0` may no longer be parsed correctly. If you are using version 0.18.0 or earlier, check out a non-conflicted commit before upgrading to prevent issues. ##### Deprecations ##### New features - `jj git {push,clone,fetch}` can now spawn an external `git` subprocess, via the `git.subprocess = true` config knob. This provides an alternative that, when turned on, fixes SSH bugs when interacting with Git remotes due to `libgit2`s limitations [#4979](jj-vcs/jj#4979). - `jj describe` now accepts `--edit`. - `jj evolog` and `jj op log` now accept `--reversed`. - `jj restore` now supports `-i`/`--interactive` selection. - `jj file list` now supports templating. - There is a new `builtin_op_log_oneline` template alias you can pass to `jj op log -T` for a more compact output. You can use `format_operation_oneline` and `format_snapshot_operation_oneline` to customize parts of it. - New template function `config(name)` to access to configuration variable from template. - New template function `pad_centered()` to center content within a minimum width. - Templater now supports `list.filter(|x| ..)` method. - The `diff` commit template keyword now supports custom formatting via `diff.files()`. For example, `diff.files().map(|e| e.path().display())` prints changed file paths. - The `diff.stat()` template method now provides methods to get summary values. - `jj log` can now show cryptographic commit signatures. The output can be controlled by the `ui.show-cryptographic-signatures=true` config knob. The signature template can be customized using `format_detailed_cryptographic_signature(signature)` and `format_short_cryptographic_signature(signature)`. - New `git.sign-on-push` config option to automatically sign commits which are being pushed to a Git remote. - New `git.push-new-bookmarks` config option to push new bookmarks without `--allow-new`. - `jj status` now shows untracked files when they reside directly under a tracked directory. There's still an issue that files under untracked directories aren't listed. [#5389](jj-vcs/jj#5389) - New `merge-tools.<TOOL>.diff-expected-exit-codes` config option to suppress warnings from tools exiting with non-zero exit codes. - New `fix.tools.TOOL.enabled` config option to enable/disable tools. This is useful for defining disabled tools in user configuration that can be enabled in individual repositories with one config setting. - Added `--into` flag to `jj restore`, similarly to `jj squash` and `jj absorb`. It is equivalent to `--to`, but `--into` is the recommended name. - Italic text is now supported. You can set e.g. `color.error = { fg = "red", italic = true }` in your config. - New `author_name`/`author_email`/`committer_name`/`committer_email(pattern)` revset functions to match either name or email field explicitly. - New `subject(pattern)` revset function that matches first line of commit descriptions. - Conditional configuration now supports `--when.commands` to change configuration based on subcommand. - The Jujutsu documentation site now publishes a schema for the official configuration file, which can be integrated into your editor for autocomplete, inline errors, and more. Please [see the documentation](/docs/config.md#json-schema-support) for more on this. ##### Fixed bugs - `jj git fetch` with multiple remotes will now fetch from all remotes before importing refs into the jj repo. This fixes a race condition where the treatment of a commit that is found in multiple fetch remotes depended on the order the remotes were specified. - Fixed diff selection by external tools with `jj split`/`commit -i FILESETS`. [#5252](jj-vcs/jj#5252) - Conditional configuration now applies when initializing new repository. [#5144](jj-vcs/jj#5144) - `[diff.<format>]` configuration now applies to `.diff().<format>()` commit template methods. - Conflicts at the end of files which don't end with a newline character are now materialized in a way that can be parsed correctly. [#3968](jj-vcs/jj#3968) - Bookmark and remote names written by `jj git clone` to `revset-aliases.'trunk()'` are now escaped if necessary. [#5359](jj-vcs/jj#5359) ##### Contributors Thanks to the people who made this release happen! - Angel Ezquerra ([@AngelEzquerra](https://github.com/AngelEzquerra)) - Antoine Martin ([@alarsyo](https://github.com/alarsyo)) - Anton Bulakh ([@necauqua](https://github.com/necauqua)) - Austin Seipp ([@thoughtpolice](https://github.com/thoughtpolice)) - Baltasar Dinis ([@bsdinis](https://github.com/bsdinis)) - Benjamin Tan ([@bnjmnt4n](https://github.com/bnjmnt4n)) - blinry ([@blinry](https://github.com/blinry)) - Bryce Berger ([@bryceberger](https://github.com/bryceberger)) - Charlie-83 ([@Charlie-83](https://github.com/Charlie-83)) - Christian Stoitner ([@cstoitner](https://github.com/cstoitner)) - Evan Martin ([@evmar](https://github.com/evmar)) - George Christou ([@gechr](https://github.com/gechr)) - Ilya Grigoriev ([@ilyagr](https://github.com/ilyagr)) - Jakob Hellermann ([@jakobhellermann](https://github.com/jakobhellermann)) - JDSeiler ([@JDSeiler](https://github.com/JDSeiler)) - Jonathan Frere ([@MrJohz](https://github.com/MrJohz)) - Jonathan Gilchrist ([@jgilchrist](https://github.com/jgilchrist)) - Josh Steadmon ([@steadmon](https://github.com/steadmon)) - Martin von Zweigbergk ([@martinvonz](https://github.com/martinvonz)) - Matt Kulukundis ([@fowles](https://github.com/fowles)) - Ollivier Robert ([@keltia](https://github.com/keltia)) - Philip Metzger ([@PhilipMetzger](https://github.com/PhilipMetzger)) - Philipp Albrecht ([@pylbrecht](https://github.com/pylbrecht)) - Robert Jackson ([@rwjblue](https://github.com/rwjblue)) - Samuel Tardieu ([@samueltardieu](https://github.com/samueltardieu)) - Scott Taylor ([@scott2000](https://github.com/scott2000)) - Stephen Jennings ([@jennings](https://github.com/jennings)) - Valentin Gatien-Baron ([@v-gb](https://github.com/v-gb)) - Vincent Ging Ho Yim ([@cenviity](https://github.com/cenviity)) - Waleed Khan ([@arxanas](https://github.com/arxanas)) - Yuya Nishihara ([@yuja](https://github.com/yuja)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

arxanas added the enhancement New feature or request label Nov 26, 2024

thoughtpolice mentioned this issue Dec 17, 2024

Getting "Error: invalid or unknown remote ssh hostkey; class=Ssh (23); code=Certificate (-17)" on MacOS #5120

Closed

arxanas added the help wanted Extra attention is needed label Dec 19, 2024

martinvonz pinned this issue Dec 19, 2024

arxanas mentioned this issue Dec 20, 2024

jj with https for a private, hosted github #5166

Closed

arxanas changed the title ~~FR: Have networked jj git commands shell out to git~~ FR: Resolve many SSH issues by having networked jj git commands shell out to git Dec 21, 2024

bsdinis mentioned this issue Jan 2, 2025

git: spawn a separate git process for network operations #5228

Merged

4 tasks

arxanas mentioned this issue Jan 2, 2025

jj git push does not try all ssh keys #5238

Open

bsdinis closed this as completed in #5228 Jan 23, 2025

BrewTestBot mentioned this issue Feb 6, 2025

jj 0.26.0 Homebrew/homebrew-core#206710

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FR: Resolve many SSH issues by having networked `jj git` commands shell out to `git` #4979

FR: Resolve many SSH issues by having networked `jj git` commands shell out to `git` #4979

arxanas commented Nov 26, 2024 •

edited by ilyagr

Loading

gulbanana commented Dec 26, 2024

arxanas commented Jan 2, 2025

arxanas commented Jan 2, 2025

emilazy commented Jan 2, 2025

gulbanana commented Jan 3, 2025

jdmarshall commented Jan 24, 2025

FR: Resolve many SSH issues by having networked jj git commands shell out to git #4979

FR: Resolve many SSH issues by having networked jj git commands shell out to git #4979

Comments

arxanas commented Nov 26, 2024 • edited by ilyagr Loading

Update: Current status

gulbanana commented Dec 26, 2024

arxanas commented Jan 2, 2025

arxanas commented Jan 2, 2025

emilazy commented Jan 2, 2025

gulbanana commented Jan 3, 2025

jdmarshall commented Jan 24, 2025

FR: Resolve many SSH issues by having networked `jj git` commands shell out to `git` #4979

FR: Resolve many SSH issues by having networked `jj git` commands shell out to `git` #4979

arxanas commented Nov 26, 2024 •

edited by ilyagr

Loading