fix exception handling of KeyboardInterrupt during startup #8182
If pants is hit with a Ctrl-C when in the engine at the right time when it starts up, it fails to handle the exception correctly, due to an incorrect
Additionally, when this occurs, the exception is invisible to the user, because the default behavior decided previously in
Both of these have led to repeated confusion from users, especially when using pantsd.
Users don't have mysterious errors when they try to quit a pants run!
blorente left a comment
+1 to having
Otherwise, this seems great! I'm assuming this is super timing-dependent, so I can't think of how to write a test that wouldn't be flaky eventually. That said, if you have ideas, I'd love to see a regression test for this!