Cryptic error message when trying to run a Daml Script against Daml Hub

Questions
1

I’m trying to run a Daml Script against a running Daml Hub ledger, and get the following error message:

% daml script --participant-config ./participants.json --json-api --dar ./../.packages/init/.daml/dist/sor-mvp-init-0.0.1.dar --script-name Init.Carrier:initCarrierRole --input-file ./onboard_carrier_input.json.V30 --output-file ./initCarrier_result.json
Exception in thread "main" java.util.NoSuchElementException: None.get
        at scala.None$.get(Option.scala:627)
        at scala.None$.get(Option.scala:626)
        at com.daml.lf.engine.script.RunnerMain$.$anonfun$main$9(RunnerMain.scala:108)
        at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:467)
        at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:63)
        at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:100)
        at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18)
        at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:94)
        at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:100)
        at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:49)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48)
        at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
        at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
        at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
        at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
        at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)

What can it mean?

I’ve checked the usual suspects like input type of the Daml Script seems to match the input json, and participants.json is good.

2 Likes
2

That’s a bug in SDK 2.3. It will be fixed in SDK 2.4. In the meantime, try using the script runner from SDK 2.2.

2 Likes
3

Thank you!