mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
2035a34a0e
Summary: Our higher-level goal is to get rid of `CommitSyncOutcome::Preserved` altogether. This diff is a step in that direction. Specifically, this diff removes the creation of "accidental" Preserved commits: the ones where the hashes are identical, although a `Mover` of some version have been applied. There are a few sides to this fix: - `get_commit_sync_outcome` now returns `Preserved` only when the source and target hashes are identical, plus stored version is `None` (previously it would only look at hashes). - `sync_commit_no_parents` now records the `Mover` version it used to rewrite the commit (previously it did not, which would sometimes create `Preserved` roots) - there are now just two ways to sync commits as `Preserved`: - `unsafe_preserve_commit` (when the caller explicitly asks for it). The idea is to only remove it once we remove the callers of this methods, of course. - `sync_commit_single_parent` when the parent is also `Preserved`. Note that automatically upgrading from `Preserved` parent to a rewritten changeset is incorrect for now: `Preserved` does not have an associated version by definition, so we would have to use a current version, which may corrupt the repo. Once we get rid of `Preserved`, this case will naturally go away. - as we now have `update_mapping_with_version` and `update_mapping` (which consumes current version), we need to add explicit `update_mapping_no_version` for preserved commits we are still creating (again, recording a current version is a mistake here, same reason as above) NB: I've added/changed a bunch of `println`s in tests, leaving them here, as they are genuinely useful IMO and not harmful. Reviewed By: StanislavGlebik Differential Revision: D24142837 fbshipit-source-id: 2153d3c5cc406b3410eadbdfca370f79d01471f9 |
||
|---|---|---|
| .. | ||
| 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 | ||
| mercurial | ||
| metaconfig | ||
| microwave | ||
| mononoke_api | ||
| mononoke_commitcloud_bookmarks_filler | ||
| mononoke_hg_sync_job | ||
| mononoke_types | ||
| mutable_counters | ||
| newfilenodes | ||
| permission_checker | ||
| phases | ||
| pushrebase | ||
| reachabilityindex | ||
| regenerate_hg_filenodes | ||
| repo_client | ||
| repo_import | ||
| revset | ||
| scs_server | ||
| 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