##// END OF EJS Templates
lfs: narrow the exceptions that trigger a transfer retry...
lfs: narrow the exceptions that trigger a transfer retry The retries were added to workaround TCP RESETs in fb-experimental fc8c131314a9. I have no idea if that's been debugged yet, but this wide net caught local I/O errors, bad hostnames and other things that shouldn't be retried. The next patch will validate objects as they are uploaded, and there's no need to retry those errors. The spec[1] does mention that certain http errors can be retried, including 500. But let's work through the corruption detection issues first. [1] https://github.com/git-lfs/git-lfs/blob/master/docs/api/batch.md

File last commit:

r18526:9409aeaa stable
r35491:b0c01a5e default
Show More
notfound.tmpl
18 lines | 397 B | application/x-cheetah | CheetahLexer
{header}
<title>Mercurial repository not found</title>
</head>
<body>
<div class="page_header">
<a href="{logourl}" title="Mercurial" style="float: right;">Mercurial</a> Not found: {repo|escape}
</div>
<div class="page_body">
The specified repository "{repo|escape}" is unknown, sorry.
<br/>
<br/>
Please go back to the <a href="{url|urlescape}">main repository list page</a>.
</div>
{footer}