8ef5d4ba64
Summary: File content blobs are thrift encoded in Mononoke. This is done so that we can change the encoding of content blobs easily. For example, we can add compression or we can add split the blobs in chunks. However there is a problem. At the moment file content blob key is a hash of the actual data that's written to blobstore i.e. of a thrift encoded data. That means that if we add compression or change thrift encoding in any way, then the file content blob key changes and it changes the commit hashes. This is wrong. To fix it let's use hash of the actual file content as the key. Reviewed By: farnz Differential Revision: D12884898 fbshipit-source-id: e60a7b326c39dad86e2b26c6f637defcb0acc8e8 |
||
---|---|---|
apiserver | ||
async-compression | ||
asyncmemo | ||
blobrepo | ||
blobrepo_utils | ||
blobstore | ||
blobstore-sync-queue | ||
bonsai-hg-mapping | ||
bonsai-utils | ||
bookmarks | ||
bundle2-resolver | ||
bytes-ext | ||
cache-warmup/src | ||
changesets | ||
cmdlib/src | ||
cmds | ||
common | ||
eden_server | ||
failure_ext | ||
filenodes | ||
futures-ext | ||
hgcli | ||
hgproto | ||
hook_tailer | ||
hooks | ||
mercurial | ||
mercurial-bundles | ||
mercurial-types | ||
metaconfig | ||
mononoke-api/src | ||
mononoke-types | ||
netstring/src | ||
phases | ||
py_tar_utils | ||
reachabilityindex | ||
ready_state/src | ||
repo_client | ||
revset | ||
server | ||
sshrelay | ||
tests | ||
.gitignore | ||
.travis.yml | ||
Cargo.toml | ||
CONTRIBUTING.md | ||
LICENSE | ||
packman.yml | ||
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.