Merge pull request #5229 from palas/prepare-for-wasm
Prepare for wasm
Prepare for wasm
ChainSync Timeouts
Allow using `QuickCheck < 2.16`
For not, '-Wno-redundant-constraints' is needed in testing libraries to prevent false-positives that lead to build errors with `-Werror`. See https://gitlab.haskell.org/ghc/ghc/-/issues/24173 for details.
For not, '-Wno-redundant-constraints' is needed in testing libraries to prevent false-positives that lead to build errors with `-Werror`. See https://gitlab.haskell.org/ghc/ghc/-/issues/24173 for details.
* permanent indexes * more efficient `mempoolHasTx` operation using `mempoolSet` membership check.
For not, '-Wno-redundant-constraints' is needed in testing libraries to prevent false-positives that lead to build errors with `-Werror`. See https://gitlab.haskell.org/ghc/ghc/-/issues/24173 for details.
- Move timeLimitsChainSync to Cardano.Network.Protocol.ChainSync.Codec.TimeLimits - Add PeerTrustable parameter to timeLimitsChainSync and adjust timeout behavior for trusted peers - Bump minChainSyncTimeout to 601 and maxChainSyncTimeout to 911 - Add extraFlag type variable to various contexts and handles for extensibility - Add extraFlags parameter to peer selection and connection management functions - Add property tests for timeLimitsChainSync timeout validation
Allow using `QuickCheck < 2.16`
For not, '-Wno-redundant-constraints' is needed in testing libraries to prevent false-positives that lead to build errors with `-Werror`. See https://gitlab.haskell.org/ghc/ghc/-/issues/24173 for details.
Two generator functions were generating absurdly long lists of trace events. These very long lists would then cause heap exhaustion then they were checked. The solution was to add a maximum length partameter to these functions and then add a max list length of 10000 to all the calling sites.