mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 16:57:49 +03:00
450073c203
Summary: The diff only contains HgCommand signatures. No implementation yet. The purpose of the getcommitdata command is to return the serialized contents of a commit. Given a Mercurial Changelog Id, the endpoint returns the same contents that the Revlog would return on a Mercurial server. At this point I am looking for suggestions regarding the protocol and the implementation. My assumption is that both request and response can be fully kept in memory. I think that we may decide that the request is going to be streamed to the client so the initial protocol allows for that. Requirements: Input: HgChangelogId Output: Changelog entry contents Protocol Summary: ``` Request: "getcommitdata" LF "nodes " Length LF Length*(HEXDIG|" ") Response: *(40HEXDIG Length LF Length*(%x00-79) LF) ``` A bit of a silly protocol. Let me know what recommendations you have. The Request is modelled after the "known" command. This allows for efficient batching compared to a batch command model. It's a bit awkward that we don't pass in the number of HgChangelogId entries that we have in the request but that is the existing protocol. For every HgChangelogId in the request the response will first have a line with the HgChangelogId that was requested and the length of the contents. The next line will contain the contents followed by line feed. Reviewed By: krallin Differential Revision: D20345367 fbshipit-source-id: 50dffff4f6c60396f564f2f1f519744ce730bf96 |
||
|---|---|---|
| .. | ||
| apiserver | ||
| benchmark | ||
| blobimport_lib/src | ||
| blobrepo | ||
| blobrepo_utils | ||
| blobstore | ||
| blobstore_sync_queue | ||
| bonsai_git_mapping | ||
| bonsai_globalrev_mapping | ||
| bonsai_hg_mapping | ||
| bookmarks | ||
| cache_warmup/src | ||
| changesets | ||
| cmdlib | ||
| cmds | ||
| commit_rewriting | ||
| common | ||
| config_structs/repos | ||
| derived_data | ||
| edenapi_server/src | ||
| fastreplay/src | ||
| filenodes | ||
| filestore/src | ||
| git | ||
| gotham_ext/src | ||
| hgcli | ||
| hgproto | ||
| hook_tailer | ||
| hooks | ||
| lfs_import_lib/src | ||
| lfs_protocol | ||
| lfs_server/src | ||
| manifest | ||
| mercurial | ||
| metaconfig | ||
| microwave | ||
| mononoke_api/src | ||
| mononoke_types | ||
| newfilenodes | ||
| phases | ||
| pushrebase/src | ||
| reachabilityindex | ||
| repo_client | ||
| revset | ||
| scs_server/src | ||
| segmented_changelog/src | ||
| server | ||
| sshrelay | ||
| tests | ||
| walker/src | ||
| 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