Respect Keyboard interrupt

[GregJohnStewart]

Hello, it does not currently seem possible to cancel a run via ctrl+C, at least quickly. An update should be made to capture this input and appropriately force-cancel the run.

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[jwmatthews]

Thank you @GregJohnStewart for the issue.

I am assuming that this was directed against "kantra", I confirmed I also am unable to ctrl-c to break out of a run once it's processing rules. With the below, I was able to ctrl-c in the first few seconds of startup and it was honored, once it got into processing rules it looked like the ctrl-c hung the process, it failed to continue to process rules and failed to exit.

$ time kantra analyze --input "./forklift-console-plugin" --output "./workdir/round-3-debug/kantra" --overwrite --provider nodejs --source patternfly-v5 --target patternfly-v6 --rules ./rulesets --enable-default-rulesets=false > ./workdir/round-3-debug/kantra-run.log
Running source analysis...
  ✓ Created volume
  ✓ Started provider containers
  ✓ Initialized providers (builtin, nodejs)
  ✓ Started rules engine
  ✓ Preparing nodejs provider   0% |░░░░░░░░░░░░░░░░░░░░░░░░░| 15/1957 files^CERRO[0014] unable to prepare provider                    error="rpc error: code = Canceled desc = context canceled" provider=nodejs
^C^C^C^C

<waited 90s, still did not quit>

[jwmatthews]

@GregJohnStewart I transfered this issue to the kantra repository based on the assumption that is what you were running. If this is incorrect, please let us know.

[GregJohnStewart]

That is accurate, the upfront cancel vs after rules.

Yeah I was not 100% where to put this. And technically I'm running the mta/ mta-cli, so wherever the relevant utility is.