##// END OF EJS Templates
exchange: raise error.Abort instead of ValueError...
exchange: raise error.Abort instead of ValueError Raising ValueError results in an uncaught exception and a traceback being printed. In the context of servers, it can result in an HTTP 500 and an exception being logged in the error log. I don't think this is proper behavior. The bundle2 code paths have a mechanism for translating an error.Abort into an error message reported to the clients. I think we should use that instead. This commit replaces some ValueError with Abort so that servers can error more gracefully. Differential Revision: https://phab.mercurial-scm.org/D5972

File last commit:

r39526:96695095 default
r41853:3b0ba457 default
Show More
PURPOSE
9 lines | 396 B | text/plain | TextLexer
This directory is meant to cache artifacts useful for tests (such as bundle).
Those artifacts need to be cached because they are slow to regenerate on each
test but too large to be tracked within the repository. They are not expected
to change between each run and can be cached.
The `./scripts/` contains code to generate the artifact while the `cache`
directory contains resulting artifact.