Mercurial > hg
view rust/chg/Cargo.toml @ 40655:69d4c8c5c25e stable
subrepo: print the status line before creating the peer for better diagnostics
I ran into a problem where I tried updating to a different branch, and the
process appeared to hang. It turned out that the subrepo revision wasn't
available locally, and I must have originally cloned it from an `hg serve -S` on
a machine that currently wasn't serving anything. It took 2+ minutes to
timeout, and didn't mention what it was connecting to even then.
There are a couple of other issues in this scenario too.
- The repo is dirty after the failed checkout because the top level repo is
updated first. We should probably make 2 passes- top down to pull
everything needed, and then do an update once everything is in place.
- Something must be reading .hgsubstate from wdir because if the same merge
command is run after the timeout, a prompt is issued that the local and
remote subrepo diverged, instead of hanging. But it lists the local version
and remote version as having the same hash.
author | Matt Harbison <matt_harbison@yahoo.com> |
---|---|
date | Fri, 16 Nov 2018 18:37:26 -0500 |
parents | 7623199def92 |
children | 1c385b99a360 |
line wrap: on
line source
[package] name = "chg" version = "0.1.0" authors = ["Yuya Nishihara <yuya@tcha.org>"] description = "Client for Mercurial command server with cHg extension" license = "GPL-2.0+" [dependencies] bytes = "0.4" futures = "0.1" libc = "0.2" log = { version = "0.4", features = ["std"] } tokio = "0.1" tokio-hglib = "0.2" # TODO: "^0.2.3" once released. we need AsRawFd support. tokio-process = { git = "https://github.com/alexcrichton/tokio-process" } tokio-timer = "0.2" [build-dependencies] cc = "1.0"