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

r23399:fd5247a8 default
r35490:16660fd4 default
Show More
Dockerfile
23 lines | 520 B | text/x-dockerfile-config | DockerLexer
FROM debian:wheezy
ENV DEBIAN_FRONTEND noninteractive
ENV WSGI_PROCESSES 4
ENV WSGI_THREADS 1
ENV WSGI_MAX_REQUESTS 100000
EXPOSE 80
VOLUME ["/var/hg/htdocs", "/var/hg/repos"]
RUN apt-get update && apt-get -y install libapache2-mod-wsgi python-dev vim
# Install our own Apache site.
RUN a2dissite 000-default
ADD vhost.conf /etc/apache2/sites-available/hg
RUN a2ensite hg
ADD hgwebconfig /defaulthgwebconfig
ADD entrypoint.sh /entrypoint.sh
ENTRYPOINT ["/entrypoint.sh"]
CMD ["/usr/sbin/apache2", "-DFOREGROUND"]