0f229aff4c
Summary: By design, the mutation history of a commit should not have any cycles. However, synthetic entries created by backfilling obsmarkers may inadvertently create erroneous cycles, which must be correctly ignored by the mutation store. The mutation store is affected by cycles in two ways: * Self-referential entries (created by backfilling "revive" obsmarkers) must be dropped early on, as these will overwrite any real mutation data for that successor. * Larger cycles will prevent determination of the primordial commit for primordial optimization. Here we drop all entries that are part of the cycle. These entries will not be shareable via the mutation store. Note that it is still possible for cycles to form in the store if they are added in multiple requests - the first request with a partial cycle will allow determination of a primordial commit which is then used in subsequent requests. That's ok, as client-side cycle detection will break the cycle in these entries. As we move away from history that has been backfilled from obsmarkers, this will become less of a concern, as cycles in pure mutation data are impossible to create. Reviewed By: mitrandir77 Differential Revision: D22206318 fbshipit-source-id: a57f30a19c482c7cde01cbd26deac53b7bb5973f |
||
---|---|---|
.. | ||
backsyncer | ||
benchmark | ||
blobimport_lib | ||
blobrepo | ||
blobrepo_utils | ||
blobstore | ||
blobstore_sync_queue | ||
bonsai_git_mapping | ||
bonsai_globalrev_mapping | ||
bonsai_hg_mapping | ||
bookmarks | ||
bulkops | ||
cache_warmup | ||
changesets | ||
cmdlib | ||
cmds | ||
commit_rewriting | ||
common | ||
derived_data | ||
edenapi_server | ||
fastreplay | ||
filenodes | ||
filestore | ||
git | ||
gotham_ext | ||
hgcli | ||
hgproto | ||
hook_tailer | ||
hooks | ||
lfs_import_lib | ||
lfs_protocol | ||
lfs_server | ||
load_limiter | ||
manifest | ||
megarepolib | ||
mercurial | ||
metaconfig | ||
microwave | ||
mononoke_api | ||
mononoke_types | ||
mutable_counters | ||
newfilenodes | ||
permission_checker | ||
phases | ||
pushrebase | ||
reachabilityindex | ||
repo_client | ||
repo_import | ||
revset | ||
scs_server/src | ||
segmented_changelog | ||
server | ||
sshrelay | ||
tests | ||
time_window_counter | ||
tunables | ||
unbundle_replay | ||
walker | ||
Cargo.toml | ||
README.md |
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.
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