Jun Wu ea0ffd3607 treemanifest: make post-pull prefetch non-fatal ... Summary: Similar to D19957251, failing to prefetch trees post-pull is not a fatal error. This recently became an issue because with these conditions: - We're migrating a repo from hg to Mononoke, and Mononoke has lagged bookmarks, esp. remote/master. - We're still using Mercurial to serve infinitepush pulls (ex. scratch bookmarks). Mercurial will return bookmarks that are not synced to Mononoke yet. - I made a recent change (D20531121) that moves selectivepull logic that changes `pull -r HASH` to `pull -r HASH -B master` to core. The CI tier didn't have selectivepull enabled that will pull bookmarks, but now they also pull bookmarks. - The tree prefetch logic uses unpatched paths.default to fetch `master`, which can be an unknown commit for Mononoke. Ideally, the final state is to rely on Mononoke for everything. There is only `paths.default` which points to Mononoke. For now, as a temporary fix let's just make post-pull tree prefetch non-fatal. Once this happens, it will be logged to the cloud table with fatal=false. Reviewed By: krallin Differential Revision: D20873599 fbshipit-source-id: 291a2dc41c7c602f004ad8df71e19a48a98e9c5e		2020-04-06 14:04:51 -07:00
..
__init__.py	treemanifest: make post-pull prefetch non-fatal	2020-04-06 14:04:51 -07:00