-
Notifications
You must be signed in to change notification settings - Fork 13
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
Got error in jupyter lab #2
Comments
Hey, thanks for the report I don't have a mac machine close by, but I must admit I also did not fiddle with jupyter lab. |
Hey, could you recreate the error using ILUA_LOG_LEVEL=debug jupyterlab --debug and put your output here? (console & UI errors) |
The ilua in bash works well. The console and UI always report such error after several executing.
|
ILUA_LOG_LEVEL is a environment variable that when set, will configure ILua to pump up verbose messages. prepending ILUA_LOG_LEVEL=debug to jupyter lab should pass it to ILua, and it will post log messages to the jupyter log conosole. Anyways, I must say I tried to recreate the error on linux and failed. By looking at your error I guess that some component (the kernel, or at least the interpreter communication pipe handlers) of the program died prematurely, and there are two possible sources for that:
Anyway I should work on emitting more indicative exception messages as I spot that your error could be improved to become less cryptic. I will work on that on the upcoming release, so please stay tuned! |
Thank you.
(local language was translated) |
Interesting, working on it. One last request though: what version of jupyter-lab do you use? could you please post the output of something like pip freeze | grep jupyter |
I use the latest version.
|
What about your work? I also found the error in bash that was not met before. Just keep with your schedule. I am OK, I am using |
That is interesting, because I merely added some trivial sqlite code on executions. Anyway, I bashed around the repo a bit and made the errors clearer. Only problem is I did not create a new release. Could you please clone the repo, follow the dev setup instructions in the README, run ilua with debug output (ILUA_LOG_LEVEL=debug) and post the new errors? |
I caught it in the dev version! There is difference between dev and old versions.
And before the output, I got 2019-01-03T16:53:08+0800 [ilua.proto.OutputCapture#debug] Received stdout data: b"lua: ...william/Programming/myGithub/ilua/ilua/ext/netstring.lua:63: assertion failed!\nstack traceback:\n\t[C]: in function 'assert'\n\t...william/Programming/myGithub/ilua/ilua/ext/netstring.lua:63: in function 'ext.netstring.read'\n\t/Users/william/Programming/myGithub/ilua/ilua/interp.lua:155: in main chunk\n\t[C]: in ?\n" The error appears more early, after several tests. |
@guysv I have tested the latest version. It work well in shell, but it still reported the error. The shell would also brake down if I injected a code "stream:read(1)" in |
Where did you add 'stream:read'? stream is indeed a file object (a named pipe file in our case). anyway the whole netstring part is very delicate. a single byte going to the wrong place will ruin stuff for sure.
do you mean in jupyter-lab? |
in |
Hi, I am trying to use ILua in Jupyter notebook on macOS. It has the similar error as reported by @Freakwill
Like @Freakwill said, ILua works perfectly in Terminal, but not on Jupyter notebook/console. I tried notebook itself and also Jupyter lab, the error message is the same. Is there any solution for that? |
My Jupyter notebook/lab versions
|
@HuangJunye Hi, unfortunately it seems like this issue only reproduces on macs. |
@guysv I am not sure I am competent enough to debug it. But I will try. Will update here if I figure out anything. |
@guysv I am also having issues when executing commands in macOS. It happens randomly after executing a command (quite often though). For me the error happens when reading the chars of the message in netstring.lua the assertion fails. More precisely, here: Line 63 in aa3a29e
I guess that's because the |
Good News! I finally got my hands on a macbook, expect a solution soon! |
Got error in jupyter lab. The console works well.
To my surprise, it would run well at first time, but then it always reports the following error.
My system is macOS10
The text was updated successfully, but these errors were encountered: