search

astahlman / ob-async

Asynchronous src_block execution for org-babel
343 stars 32 forks source link

Conflicting with ob-ipython but no ipython src block is in affect. #4

Closed Xparx closed 7 years ago

Xparx commented 7 years ago

Hi,

Running GNU Emacs 26.0.50.2 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 2017-02-15

When trying out this package I got the following issue error in process sentinel: async-handle-result: Cannot open load file: No such file or directory, ob-ipython

for the following orgmode buffer, trying to evaluate the sh block with :async

#+begin_src emacs-lisp
(add-to-list 'org-ctrl-c-ctrl-c-hook 'ob-async-org-babel-execute-src-block)
#+end_src

#+RESULTS:
| ob-async-org-babel-execute-src-block |

#+begin_src sh :async
sleep 3s && echo 'Done!'
#+end_src

#+RESULTS:
: 7844d44267638078301c3e39bca2bf9d

I'm using https://github.com/gregsexton/ob-ipython but I'm not evaluating a ipython block. As can bee seen the id is generate and put in place but the results never get run. The code block works without the :async argument as expected.

Hopefully this is something minor and if I could get some input on how to find the issue or give some more info to fix this, let me know.

astahlman commented 7 years ago

Hmmm, sounds like for some reason the Emacs subprocess isn't able to load the ob-ipython package. How are you loading this package?

I'd suggest turning on async debugging like this: (setq async-debug t). Now when you execute the src block the emacs-lisp that is sent to the Emacs subprocess will be logged in the Messages buffer. Then you can paste that code into an emacs -Q session and step through it with edebug to find where it's going wrong.

Let us know how it goes.

Xparx commented 7 years ago

Thanks for the info! I will dig some more. I'm not sure why ob-ipython can't be found. Emacs can find it fine with load-library.

astahlman commented 7 years ago

I've just added an interactive troubleshooting guide which may help.

Xparx commented 7 years ago

Thank you very much. This will be very helpful. I will use it when digging into this issue.

astahlman commented 7 years ago

Closing due to inactivity. Feel free to reopen after you've gone through the troubleshooting guide.

Xparx commented 7 years ago

Definitely! Time's not on my side here =). Will get back to this when it's possible.