Validator doesn't stop when it should

[konstin]

When pressing ctrl+c / ctrl+shift+c in the terminal, the application receives a keyboard interrupt. Most applications stop on the first or second time they receive that signal, but the validator just prints a stacktrace and caries on. Instead, the validator should abort on the first keyboard interrupt

[eFrane]

This was a bug related to liboparl and has since been solved.

[eFrane]

Unfortunately, this bug still exists. Whenever the validator can't exit cleanly,
it takes several SIGTERM signals to make it stop.

[konstin]

FYI this isn't specific to the validator but seems to be happening with python programs using liboparl, so it seems to be more of a liboparl than a validator bug.

[eFrane]

There's issues with breaking out of the threads now.
These should be mitigatable by actually using some sort
of thread pool and listening to the SIGABRT/SIGKILL signals,
then we could "force-join" the running threads.