Summary:
**Context:** I want to allow config changes to decide between DMv1 and v2, so I need to make usages more generic.
This diff makes it so `ChangesetPathHistoryContext` doesn't actually store any deleted manifest ids, and instead work with futures that resolve directly to the linknodes.
This makes it easier for us to use this class with DMv2, without need wrapper types around ids.
This also makes things slightly faster on repeated calls, as it caches the whole linknode, not just the id to then load the linknode from.
Reviewed By: mitrandir77
Differential Revision: D35779796
fbshipit-source-id: def93a62974cdfe02fd5e40c1c29ec49274c91ce
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 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 is omitting some functions.
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:
Support for running thrift based apis.
Production metadata SQL support (e.g. something like a MySQL backend). We provide sqlite in OSS for now.
Production blobstore storage backends (e.g. something like S3). We provide SQL (on sqlite) and File System backends currently in OSS.
Linux is Mononoke's primary target plaform with OSS CI also running on MacOS. Other Unix-like OSes may be supported in the future.
Subsystem Docs
Most of our documentation is in internal systems, however a few subsystems have in-repo markdown docs available:
72ea20ab37