Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Async execution impossible after kernel kill #205

Open
moritzschaefer opened this issue Apr 15, 2019 · 1 comment
Open

Async execution impossible after kernel kill #205

moritzschaefer opened this issue Apr 15, 2019 · 1 comment

Comments

@moritzschaefer
Copy link

When killing a kernel (ob-ipython-kill-kernel), it is impossible to run async code blocks. They will be put to the execution queue (ob-ipython--async-queue), yet execution does not start.
The reason for this is that ob-ipython-kill-kernel kills the kernel, but not the main ipython process.
As a result, when a new async block is executed, it detects two things:

  • There is a running process
  • There are elements in the async queue already
    Based on these two observations it is inferred that there is some python code cell running at the moment and nothing should be done (but putting the planned execution in the queue).

Suggested solutions:

  • ob-ipython-kill-kernel should kill both the kernel, and the ipython process
  • ob-ipython-kill-kernel should empty the ob-ipython-async-queue

I just had a brief look at the relevant code am not so familiar with it so I'm curious what others think of this issue

@moritzschaefer
Copy link
Author

Unfortunately there is nothing like a "reset button" for the whole system (at least I am not aware of it). So the only possibility to fix things is to restart emacs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant