Summary

This is a maintenance release that addresses several issues.

What’s New

• An enhancement was made to a component called TaskScheduler that could result in a collection growing significantly and, in the worst case, triggering an Out Of Memory condition.  This has been fixed.
• The Canton monitoring of metrics could unexpectedly stop due to a race condition bug that has been fixed.
• Fixed a bug in multi-package build feature where the source: field was defined in a daml.yaml.  It is  recommended that users have a separate folder for daml files.
• The dar path in the upgrades: field is now considered a dependency by multi-package build, such that daml build --all builds the dar if the upgrade field’s dar changed.
• In LF 1.15, a name collision error condition was prematurely triggered that was only applicable to LF 1.16.

Download and Installation 

The Daml 2.9.3 SDK has been released. You can install it using the command: daml install 2.9.3.

The table below lists how you can download Daml Enterprise or individual components.

If you are using Oracle JVM and testing security provider signatures, note that the Canton JAR file embeds the Bouncy Castle provider as a dependency. To enable the JVM to verify the signature, put the bcprov JAR on the classpath before the Canton standalone JAR. For example:

java -cp bcprov-jdk15on-1.70.jar:canton-with-drivers-2.9.3-all.jar com.digitalasset.canton.CantonEnterpriseApp

Note: These Docker images are designed to be suitable for production use, with minimal size and attack surface. Minimal images can sometimes make debugging difficult (e.g. no shell in the containers). For convenience, we provide “debug” versions of each of the above images, which you can access by appending “-debug” to the image tag (e.g. digitalasset-docker.jfrog.io/http-json:2.9.3-debug).