Closed dotta closed 10 years ago
It looks like that one way this can happen is if you have binary incompatible binaries in the classpath (for instance, the above issue was happening to me because I was using the worksheet-runtime library compiled with Scala 2.9 on the Scala IDE for 2.10). Hence, the cause is that the additional VM we spawn for evaluating the instrumented source may fail to initialize, and hence bring the ProgramExecutor
actor to ignore any additional requests. We need to be more robust against initialization failure and report the issue to the user.
I was also doing the coursera course and experienced that a new worksheet doesn't do anything when you save it, however I didn't see anything in the scala ide log window.
I also repeatedly run into this no-evaluation-problem but IDE restart helps. ( Build id: 3.0.0-vfinal-20130320-1624-Typesafe )
Looks like there's some bad failure handling. The WorksheetsManager
is stopped because it got a message it doesn't understand. Here's the exitReason
:
UncaughtException(WorksheetManager <actor>,Some(StopRun(ScriptCompilationUnit(L/debugtest/src/test/cps.sc))),Some(scala.actors.ActorProxy@4e0de36e),java.util.NoSuchElementException: None.get)
.get
on Option. It's an Option
for a reason. :)
Not sure how I ended up in this corrupted state, but the worksheet isn't evaluating anymore because. Looks like the
ProgramExecutor
got lost.Only workaround is closing/re-opening Eclipse. I think this may actually the issue @heathermiller mentioned some of the Coursera students have experienced.