Issue with keyboard input after sis s remove_job_and_descendants SIGKILL

[Icemole]

When I do a sis s remove_job_and_descendants ... and I finish the execution early by pressing ^C (for instance, because I had mistaken the command sequence from the history), I end up with a weird state in the terminal in which I have to press a key multiple times in order for the key to appear once in the terminal.

When I get out early, some thread is still printing stuff (looking for job: ..., delete jobs? (y/N) and so on), and the issue only happens after the thread has "stopped" printing (so, when it gets to delete jobs? (y/N)), so I believe the thread could be consuming some of the input reserved for the main terminal (if that's a thing).

You could argue that I should exit properly when prompted for delete jobs?, but my instinct always tells me to leave early, so I have to train my instinct 😄 still, this doesn't remove the fact that there's something going on with the threading in sis s remove_jobs_and_descendants, since I haven't had the terminal state go wrong after any sis m.

Had this been already reported before?