Closed johncbowers closed 6 years ago
Widely varying errors on the binder. Attached is a screenshot.
Same issues appearing for me.
@johncbowers thank you for the very detailed report. I still don't know how I never managed to run into these problems in my own testing given how common it is that they appear.
The "No result with key
" error looks like a duplicate of #24 which was fixed on master but still not in a release. The "Incomplete input
" gibberish looks like a duplicate of #23 which is also fixed but not in a release yet.
As it appears this is for a class (which I believe many users of this project are using it for teaching) and the school year is beginning, if I can't find a fix for the 3rd error I'm looking into today, I'll just release these fixes so you will have something stable and working in time.
This error is occurring locally on machines which we installed IJava on and on a fresh binder installation created directly from the SpencerPark/ijava-binder base.
History:
Steps to reproduce.
in the input field and hit SHIFT+ENTER.
In Binder, I have had two results from these actions. The first time, I got the following stack trace:
java.lang.IllegalStateException: No result with key: 0 at io.github.spencerpark.ijava.execution.IJavaExecutionControl.takeResult(IJavaExecutionControl.java:80) at io.github.spencerpark.ijava.execution.CodeEvaluator.evalSingle(CodeEvaluator.java:78) at io.github.spencerpark.ijava.execution.CodeEvaluator.eval(CodeEvaluator.java:122) at io.github.spencerpark.ijava.JavaKernel.evalRaw(JavaKernel.java:251) at io.github.spencerpark.ijava.JavaKernel.eval(JavaKernel.java:256) at io.github.spencerpark.jupyter.kernel.BaseKernel.handleExecuteRequest(BaseKernel.java:307) at io.github.spencerpark.jupyter.channels.ShellChannel.lambda$bind$16(ShellChannel.java:54) at java.base/java.lang.Thread.run(Thread.java:844) at io.github.spencerpark.jupyter.channels.Loop.run(Loop.java:44)
The second time, binder hanged and eventually turned into a completely white webpage (some black text temporarily flashed on the screen that appeared to be an error, but its gone). Actually now I can't hit it at all.
On our Mint machines, we are simply launching
jupyter notebook
, entering the same Java code as above, and receiving the same stack trace.