Type Members

1.  final case class RemoteClock(remoteApi: FullClientConfig) extends ClockConfig with UniformCantonConfigValidation with Product with Serializable

   Configure Canton to use a remote clock

   Configure Canton to use a remote clock

   In crash recovery testing scenarios, we want several processes to use the same time. In most cases, we can rely on NTP and the host clock. However, in cases where we test static time, we need the spawn processes to access the main processes clock. For such cases we can use a remote clock. However, no user should ever require this.

   remoteApi

   admin-port of the node to read the time from

2.  final case class WallClock(skews: Map[String, FiniteDuration] = Map.empty) extends ClockConfig with UniformCantonConfigValidation with Product with Serializable

   Configure Canton to use the wall clock (default)

   Configure Canton to use the wall clock (default)

   skews

   map of clock skews, indexed by node name (used for testing, default empty) Any node whose name is contained in the map will use a WallClock, but the time of the clock will by shifted by the associated duration, which can be positive or negative. The clock shift will be constant during the life of the node.