-
Notifications
You must be signed in to change notification settings - Fork 87
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Updated cabal.project file * ouroboros-network-framework: updated against typed-protocols changes * ouroboros-network-framework: stateful driver implementation * ouroboros-network-framework: added unbounded buffered channel * ouroboros-network-framework: added runConnectedPeersWithLimits * ouroboros-network-framework: extend driver tests Using PingPong protocol to test the driver. Use both `Ouroboros.Network.Driver.Simple` and `Ouroboros.Network.Driver.Limits`. Also use a ping pong client which is relaying on the `CollectSTM` primitive. The original test is renamed to fit the naming convention, which is also used in `typed-protocols-examples`. * ouroboros-network-protocols: updated against typed-protocols changes Only the main library is updated. * ouroboros-network: updated against typed-protocol changes Only the main library is updated. * ouroboros-protocol-tests: stateful cborg utilities * ouroboros-network-protocols:testlib updated against typed-protocols changes * ouroboros-network:sim-tests-lib updated against typed-prococols changes * ouroboros-network-protocols: updated cddl and benchmarks * ouroboros-network-framework: name some tvars & threads Most part of this patch is updating dependencies. * tx-submission2 tests: name client & server traces This is only useful for debugging a failing test case. * tx-submission2 tests: use unbounded channel We use pipelined client, hence we need to use an buffered channel. * block-fetch tests: fix termination of blockFetchExample1 The client side of each block-fetch protocol has to run until it's completion, otherwise it might happen that we will not generate a trace which marks completion of fetching all blocks in a batch (`CompletedFetchBatch`). This results in failure of `tracePropertyInFlight`. * block-fetch tests: fixed termination tests The first assertion of `fetchDecisionsForStateSnapshot` was triggered. We need first kill the fetch thread before the client side terminates. * tx-submission test: fixed a deadlock due to pipelining * ouroboros-network-framework: added stateful driver tests * ouroboros-network-framework: added simple driver tests * ouroboros-network-framework: reorganised Test.Ouroboros.Network.Driver module * ouroboros-network-framework: added mkMiniProtocolCbFromPeerSt This is useful API for running stateful peers. * ouroboros-network-framework: ProtocolTimeLimits ProtocolTimeLimits can be a newtype. * ouroboros-network-framework: strictness annotations in drivers * ouroboros-network:demo-chain-sync improvements * ouroboros-network-framework: relax bounds of nothunks Allow to build against nothunks-0.1; `ouroboros-consensus` and `plutus-core` do not yet use `nothunks-0.2`. * MiniProtocolParameters: use NumTxIdsToAck This ought to be part of the PR which introduced `NumTxIdsToAck`. * block-fetch tests: use `===` over `==` * Updated CHANGELOG.md files * ouroboros-network-framework: updated stateful driver test * typed-protocols-0.3.0.0 typed-protocols-0.3.0.0 provide better stateful API, which allows us to decouple `Message` type from it encoding. This is used to remove `query resesult` field of `MsgResp` of the `LocalStateQuery` mini-protocol. * ouroboros-network-protocols:testlib removed unused constraints * flake.nix: increased heap limit
- Loading branch information
Showing
100 changed files
with
3,355 additions
and
2,342 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.