What happened?

A donkey executes/evals code which could have infinite loop but it doesn't necessarily stop the donkey from accepting new code to execute/evaluate.

Currently, because the donkey uses a shared interpreter, the next execution/evaluation cannot happen because the donkey is stuck fulfilling the previous task.

We should be smart about infinite loops or code stuck and be able to kill the previous worker behind the scene and start a new one when repeated execute/eval are demanded, otherwise the whole use case would be stuck forever.

Users have a chance to opt-in for awaiting each donkey execution/evaluation, but that shouldn't be mandatory and, if it is, there's no way to get out that awaiting state from the code.

What browsers are you seeing the problem on? (if applicable)

No response

Console info

No response

Additional Context

No response