Stanislau Hlebik b1a4f2f7be mononoke: treat missing nodes differently in walker ... Summary: Current we treat missing just as any other error, and that makes it hard to have an alarm on blobs that are missing, because any transient error might make this alarm go off. Let's instead differentiate between a blob being missing and failed to fetch a blob because of any other error (i.e. manifold is unavaialble). Turned out this is not too difficult to do because a lot of the types implement Loadable trait, which has Missing variant in its errors. side-note: It looks like we have 3 steps which treat missing blobs as not being an error. These steps are: 1) fastlog_dir_step 2) fastlog_file_step 3) hg_filenode_step I think this is wrong, and I plan to fix it in the next diff Reviewed By: ahornby Differential Revision: D27400280 fbshipit-source-id: e79fff25c41e4d03d77b72b410d6d2f0822c28fd		2021-03-30 07:50:31 -07:00
..
schemas	mononoke: record checkpoint update stats and finish time	2021-03-12 10:46:40 -08:00
src	mononoke: treat missing nodes differently in walker	2021-03-30 07:50:31 -07:00
Cargo.toml	Autocargo-ed serde_php (#80)	2021-03-16 07:52:34 -07:00