##// END OF EJS Templates
test-lfs: add tests around corrupted lfs objects...
test-lfs: add tests around corrupted lfs objects These are mostly tests against file:// based remote stores, because that's what we have the most control over. The test uploading a corrupt blob to lfs-test-server demonstrates an overly broad exception handler in the retry loop. A corrupt blob is actually transferred in a download, but eventually caught when it is accessed (only after it leaves the corrupt file in a couple places locally). I don't think we want to trust random 3rd party implementations, and this would be a problem if there were a `debuglfsdownload` command that simply cached the files. And given the cryptic errors, we should probably validate the file hash locally before uploading, and also after downloading.

File last commit:

r18526:9409aeaa stable
r35490:16660fd4 default
Show More
notfound.tmpl
12 lines | 262 B | application/x-cheetah | CheetahLexer
{header}
<title>Mercurial repository not found</title>
</head>
<body>
<h2>Mercurial repository not found</h2>
The specified repository "{repo|escape}" is unknown, sorry.
Please go back to the <a href="{url|urlescape}">main repository list page</a>.
{footer}