Muir Manders d68bac7192 lfs: retry fetch requests on 503 response code ... Summary: Currently a single LFS 503 during clone/checkout aborts the operation and leaves the user in a situation that is difficult to recover from. Now we treat a 503 as any other 5XX server error and retry. The 5XX retry count/backoff can be configured via the lfs.backofftimes config knob. It defaults in the code to [1, 4, 8], which is 3 retries with rand(1), rand(4) and rand(8) sleep in between. 503 can be served from proxygen indicating there are no live lfs servers, or from x2pagentd in cases of network failure. Reviewed By: quark-zju Differential Revision: D33804601 fbshipit-source-id: cbb3514051843d3517bb676cf7c83dce057e42b9		2022-02-02 17:37:32 -08:00
..
fs	teach eden doctor to recognize stale NFS mounts	2022-02-02 13:16:41 -08:00
hg-server	remove generated code for hgclientconf	2022-01-31 10:34:32 -08:00
integration	backingstore: conditionalize use of "fb" feature	2022-01-27 13:32:12 -08:00
locale
mononoke	Special-case linkfile src="."	2022-02-02 14:17:56 -08:00
scm	lfs: retry fetch requests on 503 response code	2022-02-02 17:37:32 -08:00
test_support	fs: fix license header	2022-01-04 15:00:07 -08:00
test-data	fix fsck snapshot integration tests	2021-07-14 16:20:04 -07:00
.gitignore	eden: wire up mac contbuild	2019-02-05 21:52:30 -08:00
.mononoke_test_file	test push	2022-01-06 05:57:35 -08:00
Eden.project.toml	Eden.project.toml file for Nuclide	2018-04-26 11:05:23 -07:00