Minor annoyance: Control-C on `ue4 run` raises an exception about ue4cli HOT 2 OPEN

This is a general problem with Utility class which does a bunch of I/O operations but does not catch any exceptions related to them. These for sure shouldn't be treated as success, including KeyboardInterrupt.

Interrupting a process is considered as fatal error, imagine the following case: ue4 gen && ue4 build && ue4 run Interrupting gen or build would mean that the chain is broken. If ue4cli was returning 0 in this case, that would be very unexpected.

Though, I agree these cases should be catch, since current behavior is too confusing.

Probably the easiest way to fix it is creating custom Exception for Utility class, then wrapping every I/O call with try/except block - if it fails, it should raise said custom Exception, which then can be catch inside of cli::main. This is how UnrealManagerException is being used right now to handle similar problems.

from ue4cli.

Proposed fix #65

With said change you should get something like this:

$ ue4 run
# logging from Engine...
^C
(ue4cli) Error: (KeyboardInterrupt)
# return code 1

from ue4cli.