Run script across multiple participant nodes

Questions Features & Bugs
,
1

Hi Team,

By using allocatePartyWithHintOn and a proper participant configuration file (specifying the participants and ledger-api host and port) I can successfully run script over a canton setup in 2.0.0. Here is the command I am using

daml script --dar .daml/dist/scriptOnCanton-0.0.1.dar --script-name Main:setupcanton --participant-config participants.conf

However when I tested the same setup on latest 2.3.4 (also seen in 2.3.1), I encountered an error message

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)
daml-helper: Received ExitFailure 1 when running

May I know if something new is introduced in handling daml-script running on multiple participant-node setup?

kc

1 Like
2

That’s a bug. It should be fixed in SDK 2.2 and 2.4. Only 2.3 is broken iirc.

4 Likes
3

Thanks @cocreature . I have tested the latest 2.4.0 and all the script problems I saw in 2.3 are all gone.
cheers,
kc

1 Like