Thomas Orozco e65b22d9c4 mononoke/repo_client: do not re-upload commits we already have for infinitepush ... Summary: This adds support for optionally not uploading commits we already have when they arrive via infinitepush. This can happen if we're replaying bundles. This works by filtering the commits we have. We still get some futures created for the underlying uploads, but we never poll them because when we visit what futures are needed for what commits, we don't select uploads that are only reachable from commits we filtered out. Obviously, this isn't super efficient, since the client still has to send us all this data, but it's better than having them send us all that data then having us take hours overwriting it all. Reviewed By: mitrandir77 Differential Revision: D25120844 fbshipit-source-id: f96881d0d98ec622259bedb624fd94b600a2bf1d		2020-11-20 06:30:12 -08:00
..
src	mononoke/repo_client: do not re-upload commits we already have for infinitepush	2020-11-20 06:30:12 -08:00
tunables-derive	mononoke: support history across deletions	2020-05-21 02:46:21 -07:00
Cargo.toml	Regenerate all Cargo.tomls after upgrade to futures 0.3.5	2020-07-06 20:49:43 -07:00