Closed shuangwu closed 7 years ago
Hey, will look into this soon.
Thanks for the bug report. This is an issue upstream in facebook's iTorch. They've fixed it in later commits, and I' merging them in.
Rebuilding the conda repo for iTorch, should be up soon.
Ok if you update your lua-itorch
package in conda, it should work.
Try
conda update lua-itorch -y -c alexbw
or, if that's finicky, do a fresh install of anaconda
and lua-science
Hi, I have the same problem, after trying all the above steps and using lua 5.2 as well as lua 5.3.
My original installation steps were: conda create --name lua53 --clone p35 source activate lua53 conda install lua=5.3 lua-itorch -y -c alexbw jupyter notebook
and the error is
[I 10:29:33.414 NotebookApp] Adapting to protocol v4.0 for kernel 4b134848-a6ae-45fe-9d33-70c17edd52a3 lua: ...ython/anaconda2/envs/lua53/share/lua/5.3/itorch/main.lua:350: Cannot find appropriate message handler for comm_info_request stack traceback: [C]: in function 'assert' ...ython/anaconda2/envs/lua53/share/lua/5.3/itorch/main.lua:350: in function <...ython/anaconda2/envs/lua53/share/lua/5.3/itorch/main.lua:348> (...tail calls...) ...ython/anaconda2/envs/lua53/share/lua/5.3/lzmq/poller.lua:75: in method 'poll' ...on/anaconda2/envs/lua53/share/lua/5.3/lzmq/impl/loop.lua:307: in method 'poll' ...on/anaconda2/envs/lua53/share/lua/5.3/lzmq/impl/loop.lua:325: in method 'sleep_ex' ...on/anaconda2/envs/lua53/share/lua/5.3/lzmq/impl/loop.lua:370: in method 'start' ...ython/anaconda2/envs/lua53/share/lua/5.3/itorch/main.lua:381: in main chunk [C]: in function 'require' (command line):1: in main chunk [C]: in ?
It would be great if you could have a look, as I see from the above that the upstream error should have been merged in for a long time? Many thanks in advance!!!
Try installing using Python 2.7. All of the packages were built against Python 2.7, and I haven't tested against Python 3.x
Hi, thanks for the quick answer! Gonna try when I'm back from vacation :-) Happy holidays!
I have followed the instructions in README.md on OS X, but when I run the notebook, I ran into following issue: