dc5e78c1c1
Summary: Convert scm/mononoke to use failure, and update common/rust crates it depends on as well. What it looks like is a lot of deleted code... General strategy: - common/rust/failure_ext adds some things that are in git failure that aren't yet in crates.io (`bail!` and `ensure!`, `Result<T, Error>`) - everything returns `Result<T, failure::Error>` - crates with real error get an error type, with a derived Fail implementation - replicate error-chain by defining an `enum ErrorKind` where the fields match the declared errors in the error! macro - crates with dummy error-chain (no local errors) lose it - `.chain_err()` -> `.context()` or `.with_context()` So far the only place I've needed to extract an error is in a unit test. Having a single unified error type has simplified a lot of things, and removed a lot of error type parameters, error conversion, etc, etc. Reviewed By: sid0 Differential Revision: D6446584 fbshipit-source-id: 744640ca2997d4a85513c4519017f2e2e78a73f5 |
||
|---|---|---|
| async-compression/src | ||
| asyncmemo/src | ||
| blobrepo/src | ||
| blobstore | ||
| bookmarks | ||
| cmds | ||
| eden_server/src | ||
| futures-ext/src | ||
| heads | ||
| hgcli | ||
| hgproto | ||
| hooks/src | ||
| linknodes | ||
| mercurial/src | ||
| mercurial-bundles/src | ||
| mercurial-types | ||
| metaconfig/src | ||
| py_tar_utils | ||
| repoinfo/src | ||
| revset/src | ||
| server/src | ||
| sshrelay/src | ||
| storage | ||
| tests | ||
| vfs/src | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| rustfmt.toml | ||
Mononoke
Mononoke is a next-generation server for the Mercurial source control system, meant to scale up to accepting thousands of commits every hour across millions of files. It is primarily written in the Rust programming language.
Caveat Emptor
Mononoke is still in early stages of development. We are making it available now because we plan to start making references to it from our other open source projects such as Eden.
The version that we provide on GitHub does not build yet.
This is because the code is exported verbatim from an internal repository at Facebook, and not all of the scaffolding from our internal repository can be easily extracted. The key areas where we need to shore things up are:
- Full support for a standard
cargo build. - Open source replacements for Facebook-internal services (blob store, logging etc).
The current goal is to get Mononoke working on Linux. Other Unix-like OSes may be supported in the future.