Hello Lucas, hello list, hopefully this message will thread properly.
This problem can actually be reproduced by the corresponding unit tests - at least on my "disconnected" system, the corresponding tests for the SparkInterpreter fail in exactly the same way as your code does. This is also an issue for me, since I will probably have to get those tests to pass, in order to deploy Zeppelin on our production system. Since this actually fails unit tests, I think creating a corresponding issue is a logical next step. I'm currently looking at the code of the test to figure out which component is responsible for directing the dependency lookup to the target, and how this can be overridden, but there's probably some implicit default in use, which makes figuring the root out slightly more tricky. Have you had a look at where this could be overridden yet? Filed an issue already? Unless we get some Progress going in this thread, we should start the usual procedures... Thanks and Best, Rick
