Type Members

1.  case class RemoteClock(remoteApi: ClientConfig) extends ClockConfig 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.  case class WallClock(skew: NonNegativeFiniteDuration = NonNegativeFiniteDuration.ofSeconds(0)) extends ClockConfig with Product with Serializable

   Configure Canton to use the wall clock (default)

   Configure Canton to use the wall clock (default)

   skew

   maximum simulated clock skew (0) If positive, Canton nodes will use a WallClock, but the time of the wall clocks will be shifted by a random number between -simulateMaxClockSkewMillis and simulateMaxClockSkewMillis. The clocks will never move backwards.