I'm running a cpu-bound algorithm inside a rule (detecting all cycles in a digraph) and I cannot ctrl-c out of it (this is with

--v2-ui

set, in case that matters)

@hundreds-breakfast-49010 is this expected behavior?

only for the

run

goal, but it's possible that my code that deliberately suppresses ctrl-c in the

run

goal is somehow getting executed when it shouldn't be

i think this is expected behavior actually

I was running a custom console_rule, that yielded to the rule that blocked on CPU-bound work.

the solution that greg applied for the

run

goal i think would apply here