sapling/eden/mononoke/blobrepo
Stefan Filip 310b3616a6 blobrepo: instantiate segmented changelog as an attribute
Summary:
Segmented Changelog is a component that has multiple components of each own
that each can be configured in different ways. It seems that it already is
more complicated than other components in how it is set up and it will probably
evolve to have more knobs (caching comes to mind).

Right now we have 3 ways of instantiating SegmentedChangelog:
- Disabled, all requests return errors
- ReadOnly, requests to unprocessed commits return errors
- OnDemandUpdate, requests trigger commit processing when required

Reviewed By: aslpavel

Differential Revision: D23456217

fbshipit-source-id: a6016f05197abbc3722764fa8e9056190a767b36
2020-09-02 17:20:42 -07:00
..
blobrepo_hg Fix bug with zero hash manifest 2020-08-24 07:34:29 -07:00
blobsync Regenerate all Cargo.tomls after upgrade to futures 0.3.5 2020-07-06 20:49:43 -07:00
changeset_fetcher segmented_changelog: add on-demand updating dag implementation 2020-09-02 17:20:42 -07:00
errors blobrepo: instantiate segmented changelog as an attribute 2020-09-02 17:20:42 -07:00
factory blobrepo: instantiate segmented changelog as an attribute 2020-09-02 17:20:42 -07:00
override blobrepo: move ChangesetFetcher to attributes 2020-09-02 17:20:41 -07:00
repo_blobstore Regenerate all Cargo.tomls after upgrade to futures 0.3.5 2020-07-06 20:49:43 -07:00
src blobrepo: move ChangesetFetcher to attributes 2020-09-02 17:20:41 -07:00
test RFC mononoke: limit number of filenodes get_all_filenodes_maybe_stale 2020-08-12 14:33:43 -07:00
Cargo.toml Regenerate all Cargo.tomls after upgrade to futures 0.3.5 2020-07-06 20:49:43 -07:00