mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 08:47:12 +03:00
0205634fe1
Summary: Those two have historically used different (but largely copy pasted) code to produce their responses. Let's unify them by While in there, let's also modernize the formatting a little bit by letting anyhow do the formatting for us (we used to use `failure` when this code was written, and it didn't do it). There's a bit of ugliness here in the sense that out formatting is injecting the error into the state so it can be logger later. This is equivalent to what we had, but it's kinda clonwy. That said, I'm working on refactoring our error handling in this stack, so the plan is to clean this up (i.e. it won't stay very long). Finally, note that this diff removes the `ResponseCreationFailure` error kind in LFS. This is replaced by a `.context()` in `gotham_ext`. That said, we never really use this stuff: creations are fallible in Hyper but you only run into an error if you e.g. forget to add a status code, so we don't expect them to actually occur outside of development. Reviewed By: mitrandir77 Differential Revision: D27966421 fbshipit-source-id: 097f3b69f25fe39f8fbef925a272e88199896b39 |
||
|---|---|---|
| .. | ||
| alpn | ||
| benchmarks | ||
| blobimport_lib | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| blobstore_sync_queue | ||
| bonsai_git_mapping | ||
| bonsai_globalrev_mapping | ||
| bonsai_hg_mapping | ||
| bonsai_svnrev_mapping | ||
| bookmarks | ||
| bulkops | ||
| cache_warmup | ||
| changesets | ||
| cmdlib | ||
| cmds | ||
| commit_rewriting | ||
| common | ||
| derived_data | ||
| edenapi_server | ||
| edenapi_service | ||
| fastreplay | ||
| filenodes | ||
| filestore | ||
| git | ||
| gotham_ext | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| lfs_import_lib | ||
| lfs_protocol | ||
| lfs_server | ||
| load_limiter | ||
| manifest | ||
| megarepo_api | ||
| mercurial | ||
| metaconfig | ||
| microwave | ||
| mononoke_api | ||
| mononoke_api_hg | ||
| mononoke_hg_sync_job | ||
| mononoke_types | ||
| mutable_counters | ||
| newfilenodes | ||
| observability | ||
| permission_checker | ||
| phases | ||
| pushrebase | ||
| pushrebase_mutation_mapping | ||
| quiet_stream | ||
| reachabilityindex | ||
| regenerate_hg_filenodes | ||
| repo_attributes | ||
| repo_client | ||
| repo_factory | ||
| repo_import | ||
| revset | ||
| scs_server | ||
| segmented_changelog | ||
| server | ||
| sshrelay | ||
| streaming_clone | ||
| 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