##// END OF EJS Templates
worker: raise exception instead of calling sys.exit() with child's code...
worker: raise exception instead of calling sys.exit() with child's code When a worker process returns an error code, we would call `sys.exit()` with that exit code on the main process. The `SystemExit` exception would then get caught in `scmutil.callcatch()`, which would return that error code. The comment there says "Commands shouldn't sys.exit directly", which I agree with. This patch changes it so we raise a specific exception when a worker fails so we can catch instead. I think that means that `SystemExit` is now always an internal error. (I had earlier thought that this call to `sys.exit()` was from within the child process until Matt Harbison made me look again, so thanks for that!) Differential Revision: https://phab.mercurial-scm.org/D9287

File last commit:

r38029:e51c91c1 default
r46429:8f07f5a9 default
Show More
cacerts.rc
5 lines | 161 B | text/x-stsrc | TextLexer
# This config file points Mercurial at the system-wide certificate
# store from the ca-certificates package.
[web]
cacerts = /etc/ssl/certs/ca-certificates.crt