Open Valarin opened 4 years ago
@Valarin Thanks for reporting this. I'll mark this as a bug, and please let us know if you have resolved it meanwhile and could contribute.
@Valarin @kishorebanala I might be wrong but I think below comment should solve this issue
I see that you are using Javascript arrow
function, now as it is es6
feature and if we wan't to use it we have to enable it in nashorn
while creating ScriptEngine by passing --language=es6
example:
NashornScriptEngineFactory factory = new NashornScriptEngineFactory();
ScriptEngine engine = factory.getScriptEngine("--language=es6");
But ScriptEngine is not created in this way in ScriptEvaluator.Java
and even if we implement it, you have to run it on Java 9+
env, as arrow
function within nashorn
engine is not supported in Java 8
@beatfreaker Thanks for helping debug this. In the long term, we plan to switch to Oracle GraalVM instead of Nashorn in the future versions of Conductor and will revisit this during the migration.
When WF contains Lambda task (code snippet No. 1) that fails to compile (code snippet No. 2) WF is not switched to FAILED status - it is kept in RUNNING status forever.