@@ -9,8 +9,8 @@ namespace Tests.ClientConcepts.ConnectionPooling.BuildingBlocks
99 public class DateTimeProviders
1010 {
1111 /**== Date time providers
12- *
13- * Not typically something you'll have to pass to the client but all calls to `System.DateTime.UtcNow`
12+ *
13+ * Not typically something you'll have to pass to the client but all calls to `System.DateTime.UtcNow`
1414 * in the client have been abstracted by `IDateTimeProvider`. This allows us to unit test timeouts and cluster failover
1515 * without being bound to wall clock time as calculated by using `System.DateTime.UtcNow` directly.
1616 */
@@ -29,8 +29,8 @@ [U] public void DefaultNowBehaviour()
2929 [ U ] public void DeadTimeoutCalculation ( )
3030 {
3131 var dateTimeProvider = DateTimeProvider . Default ;
32- /**
33- * The default timeout calculation is: `min(timeout * 2 ^ (attempts * 0.5 -1), maxTimeout)`, where the
32+ /**
33+ * The default timeout calculation is: `min(timeout * 2 ^ (attempts * 0.5 -1), maxTimeout)`, where the
3434 * default values for `timeout` and `maxTimeout` are
3535 */
3636 var timeout = TimeSpan . FromMinutes ( 1 ) ;
@@ -40,8 +40,8 @@ [U] public void DeadTimeoutCalculation()
4040 * Plotting these defaults looks as followed:
4141 *
4242 *[[timeout]]
43- *.Default formula, x -axis time in minutes, y -axis number of attempts to revive
44- *image::timeoutplot.png[dead timeout]
43+ *.Default formula, y -axis time in minutes, x -axis number of attempts to revive
44+ *image::timeoutplot.png[dead timeout]
4545 *
4646 * The goal here is that whenever a node is resurrected and is found to still be offline, we send it
4747 * _back to the doghouse_ for an ever increasingly long period, until we hit a bounded maximum.
@@ -52,7 +52,7 @@ [U] public void DeadTimeoutCalculation()
5252
5353 foreach ( var increasedTimeout in timeouts . Take ( 10 ) )
5454 increasedTimeout . Should ( ) . BeWithin ( maxTimeout ) ;
55-
55+
5656 }
5757
5858 }
0 commit comments