-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typed Protocols: new API #4935
Typed Protocols: new API #4935
Conversation
4b8c1f7
to
f270fd5
Compare
f270fd5
to
4242d6d
Compare
4242d6d
to
d295ced
Compare
Not related to the PR directly but I guess we could sneak it here, there's a usage binding in the module chain-sync that is not referenced anywhere - maybe we can remove it completely? |
f2cf734
to
2b81820
Compare
Which one? |
2b81820
to
234f3fc
Compare
It's this one: https://github.com/IntersectMBO/ouroboros-network/blob/coot/tx-submission/ouroboros-network/demo/chain-sync.hs#L191-L194 |
8f7be2d
to
7d73076
Compare
7d73076
to
babfabf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
1f7109a
to
240cf23
Compare
Most part of this patch is updating dependencies.
This is only useful for debugging a failing test case.
We use pipelined client, hence we need to use an buffered channel.
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`.
The first assertion of `fetchDecisionsForStateSnapshot` was triggered. We need first kill the fetch thread before the client side terminates.
This is useful API for running stateful peers.
ProtocolTimeLimits can be a newtype.
Allow to build against nothunks-0.1; `ouroboros-consensus` and `plutus-core` do not yet use `nothunks-0.2`.
This ought to be part of the PR which introduced `NumTxIdsToAck`.
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.
0adc34b
to
e66922b
Compare
# Description Use `typed-protocols-0.3.0.0`. Depends on: * [x] input-output-hk/typed-protocols#52 * [x] input-output-hk/typed-protocols#61 * [x] IntersectMBO/ouroboros-network#4935 - **Updated to use typed-protocols-0.3.0.0** - **Added KeepAlive tracer**
Description
Using input-output-hk/typed-protocols#52 & input-output-hk/typed-protocols#61.
TODO:
cabal.project
once New API for typed-protocols input-output-hk/typed-protocols#52 is published.Performance
No performance regression was found when running the benchmarking cluster using
cardano-node-9.1.0
as a base. No regression was found when syncing mainnet.Checklist
Quality
Maintenance
ouroboros-network
project.