##// 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:

r30765:eb7de21b default
r35491:b0c01a5e default
Show More
footer.tmpl
11 lines | 227 B | application/x-cheetah | CheetahLexer
<div class="page_footer">
<div class="page_footer_text">{repo|escape}</div>
<div class="rss_logo">
<a href="{url|urlescape}rss-log">RSS</a>
<a href="{url|urlescape}atom-log">Atom</a>
</div>
<br />
{motd}
</div>
</body>
</html>