A Scalable, User-Friendly Source Control System.
Go to file
Lukas Piatkowski 995e15697e bundle2-resolver: use (NodeHash, RepoPath) as id for uploaded blobs
Summary:
From upload_entry perspective NodeHash is not unique for uploaded entry, but when combined with RepoPath it is. An example are two files with the same content, but different paths.

Additionally in this diff the requirement for uploaded blobs to be unique is loosened for Manifests, because the b2xtreegroup might contain duplicates of Manifests

Reviewed By: farnz

Differential Revision: D7087863

fbshipit-source-id: 7e9c2438db037fa171f1e65b6882b445e8c09f7a
2018-02-28 11:15:01 -08:00
async-compression/src mercurial_bundles: make Bundle2Stream sendable across threads 2018-01-15 10:36:32 -08:00
asyncmemo/src asyncmemo: record all the tasks that polled the future 2018-01-19 02:18:10 -08:00
blobrepo bundle2-resolver: fetch missing file content from BlobRepo in DeltaCache 2018-02-27 11:14:52 -08:00
blobstore Introduce a LazyMemblob test blobstore 2018-02-21 07:17:00 -08:00
bookmarks Use ChangesetId rather than NodeHash in bookmarks 2018-01-22 10:23:36 -08:00
bundle2-resolver/src bundle2-resolver: use (NodeHash, RepoPath) as id for uploaded blobs 2018-02-28 11:15:01 -08:00
bytes-ext add cargo build support for local development 2018-02-22 04:30:32 -08:00
changesets Fix typos ("and and" -> "and") 2018-02-27 16:36:59 -08:00
cmds tp2: update rust-crates-io 2018-02-27 09:27:19 -08:00
common/pylz4/src mononoke: add compress function 2018-02-06 11:23:57 -08:00
eden_server/src Stop calling the deprecated bind_connection method in eden_server. 2018-02-27 11:37:59 -08:00
futures-ext/src bundle2-resolver: reorganize resolver for easier handling of BlobRepo::create_changeset 2018-02-22 04:53:56 -08:00
heads Remove Repo trait completely 2018-01-15 06:37:27 -08:00
hgcli fix test-init.t 2018-01-01 17:52:36 -08:00
hgproto mononoke: send replychangegroup to the client 2018-02-21 11:07:19 -08:00
hooks/src Replace NodeHash with ChangesetId in BlobRepo 2018-02-21 10:42:06 -08:00
linknodes mercurial-types: allow converting strs to MPaths and RepoPaths 2017-12-18 22:08:37 -08:00
mercurial/src Create changesets API in BlobRepo 2018-02-27 02:19:11 -08:00
mercurial-bundles/src mononoke: send replychangegroup to the client 2018-02-21 11:07:19 -08:00
mercurial-types tp2: update rust-crates-io 2018-02-27 09:27:19 -08:00
metaconfig/src mononoke: add repoid to BlobRepo 2018-02-26 09:43:24 -08:00
py_tar_utils move tar_utils.py from update_rust into an open sourceable location 2017-09-14 13:52:23 -07:00
repoinfo/src mononoke: use changesets table in repoinfo 2018-02-26 09:43:24 -08:00
revset/src blobrepo: make get_changeset_by_changesetid return BlobChangeset rather than Box<Changeset> 2018-02-23 11:22:58 -08:00
server/src mononoke: add repoid to BlobRepo 2018-02-26 09:43:24 -08:00
sshrelay/src Initial commit 2017-07-27 18:00:19 -07:00
storage tp2: update rust-crates-io 2018-02-27 09:27:19 -08:00
tests bundle2-resolver: use (NodeHash, RepoPath) as id for uploaded blobs 2018-02-28 11:15:01 -08:00
vfs/src mononoke: remove get_mpath and get_path and use get_name 2018-02-07 07:53:48 -08:00
CONTRIBUTING.md Initial commit 2017-07-27 18:00:19 -07:00
LICENSE Initial commit 2017-07-27 18:00:19 -07:00
README.md mention in README that Mononoke supports Mercurial 2017-07-28 14:41:37 -07:00
rustfmt.toml updates for rustfmt 0.3.4 2018-01-05 12:07:01 -08:00

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.