mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 16:57:49 +03:00
A Scalable, User-Friendly Source Control System.
b909f2bc9c
Summary: Previously we had a timeout per session i.e. multiple wireproto command will share the same timeout. It had a few disadvantages: 1) The main disadvantage was that if connection had timed out we didn't log stats such as number of files, response size etc and we didn't log parameters to scribe. The latter is even a bigger problem, because we usually want to replay requests that were slow and timed out and not the requests that finished quickly. 2) The less important disadvantage is that we have clients that do small request from the server and then keep the connection open for a long time. Eventually we kill the connection and log it as an error. With this change the connection will be open until client closes it. That might potentially be a problem, and if that's the case then we can reintroduce perconnection timeout. Initially I was planning to use tokio::util::timer to implement all the timeouts, but it has different behaviour for stream - it only allows to set per-item timeout, while we want timeout for the whole stream. (https://docs.rs/tokio/0.1/tokio/timer/struct.Timeout.html#futures-and-streams) To overcome it I implemented simple combinator StreamWithTimeout which does exactly what I want. Reviewed By: HarveyHunt Differential Revision: D13731966 fbshipit-source-id: 211240267c7568cedd18af08155d94bf9246ecc3 |
||
|---|---|---|
| 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.