|
2 | 2 | {-# LANGUAGE DerivingStrategies #-} |
3 | 3 | {-# LANGUAGE ExistentialQuantification #-} |
4 | 4 | {-# LANGUAGE NamedFieldPuns #-} |
5 | | -{-# LANGUAGE NumericUnderscores #-} |
6 | 5 | {-# LANGUAGE ScopedTypeVariables #-} |
7 | 6 |
|
8 | 7 | module Test.Consensus.Genesis.Setup.GenChains ( |
@@ -132,10 +131,11 @@ genChainsWithExtraHonestPeers genNumExtraHonest genNumForks = do |
132 | 131 | gtSlotLength, |
133 | 132 | gtChainSyncTimeouts = chainSyncTimeouts gtSlotLength asc, |
134 | 133 | gtBlockFetchTimeouts = blockFetchTimeouts, |
135 | | - gtLoPBucketParams = LoPBucketParams { lbpCapacity = 100_000, lbpRate = 1_000 }, |
136 | | - -- ^ REVIEW: Do we want to generate those randomly? For now, the chosen |
137 | | - -- values carry no special meaning. Someone needs to think about what values |
138 | | - -- would make for interesting tests. |
| 134 | + gtLoPBucketParams = LoPBucketParams { lbpCapacity = 50, lbpRate = 10 }, |
| 135 | + -- These values give little enough leeway (5s) so that some adversaries get disconnected |
| 136 | + -- by the LoP during the stalling attack test. Maybe we should design a way to override |
| 137 | + -- those values for individual tests? |
| 138 | + -- Also, we might want to generate these randomly. |
139 | 139 | gtCSJParams = CSJParams $ fromIntegral scg, |
140 | 140 | gtBlockTree = List.foldl' (flip BT.addBranch') (BT.mkTrunk goodChain) $ zipWith (genAdversarialFragment goodBlocks) [1..] alternativeChainSchemas, |
141 | 141 | gtExtraHonestPeers, |
|
0 commit comments