243826
243826
``` py4j.Py4JException: Cannot obtain a new communication channel at py4j.CallbackClient.sendCommand(CallbackClient.java:251) at py4j.CallbackClient.sendCommand(CallbackClient.java:259) at py4j.CallbackClient.sendCommand(CallbackClient.java:228) at py4j.reflection.PythonProxyHandler.invoke(PythonProxyHandler.java:107) at com.sun.proxy.$Proxy17.processInput2(Unknown Source) ``` Would be a lot better if the logging actually revealed...
Consider the following rocker snippet simplified to exemplify the problem: ``` @for((i, prop): props) { @with(String hasher = "Arrays") { @hasher.hashCode(@prop.get("key")) } } ``` I wrote that with the intent...
All the information is needed is readily available in the pom file. By using these values, we can avoid the configuration when not needed. But users invoking build.sh can still...
Currently it throws not supported exception. Unless I am missing something, to my knowledge append is supported by Hadoop.
While working with git scm, if PULL_REQUEST_TO_HASH environment variable is defined, compare the CPPCheckResults with the build which built that base as opposed to the immediately preceding one. https://issues.jenkins-ci.org/browse/JENKINS-24076