Skip to content
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

Cherry picked network changes for cardano-node-1.35.5 release #4120

Merged
merged 139 commits into from
Nov 9, 2022

Conversation

coot
Copy link
Contributor

@coot coot commented Oct 28, 2022

This cherry-picked patches from the following PRs:

Also cherry-picked almost all the commits which modify GitHub actions:

TODO:

  • bump versions of packages
  • input-output-hk/cardano-haskell-packages#84

@coot coot force-pushed the coot/cardano-node-1.35.5 branch from 47a1b86 to 44645ba Compare October 28, 2022 11:17
mtullsen and others added 29 commits October 28, 2022 13:22
Co-authored-by: Mark Tullsen <[email protected]>
Co-authored-by: Mark Tullsen <[email protected]>
We use `Established` for mini-protocols which runs for warm and hot
peers (called established in the outbound governor), `Warm` for warm
mini-protocols, `Hot` for hot mini-protocols.  This is the same naming
convention as the governor.
It just handles a single peer.
We can use 'PeerStatus' instead.
For local connections the inbound governor should not force the idleness
timeout.  Some clients relay letting the connection idle after it was
negotiated and before any mini-protocol is started.

We keep the connection manager idle timeout, this is only used for
outbound connections, and thus not related to `node-to-client` protocol.
By hiding `peerconn` we can simplify diffusion types.  This is required
if we want to add result type of protocols (on the initiator side).
ExitPolicy governs the delay for reconnecting either if any of the
mini-protocol exists cleanly or throws an exception.
When any of the mini-protocol exits (either with an error or otherwise),
we reactivation delay which is used by the outbound governor.  It is
expected that multiple mini-protocol exits roughly at the same time,
e.g.  in hot to warm transition `chain-sync`, `block-fetch` and
`tx-submission` will terminate around the same time.  For this reason
the `setActivateTimes` is taking the maximum of the existing connect time
and the new one, as well as the `ReconnectDelay` is an additive monoid.
@coot coot force-pushed the coot/cardano-node-1.35.5 branch from e246646 to fe28e03 Compare November 3, 2022 12:01
@coot coot force-pushed the coot/cardano-node-1.35.5 branch from 0628e47 to efc3d4d Compare November 8, 2022 12:14
* cardano-base
* cardano-ledger
* plutus
@coot coot force-pushed the coot/cardano-node-1.35.5 branch from efc3d4d to 56f8fdd Compare November 8, 2022 12:24
@disassembler disassembler force-pushed the coot/cardano-node-1.35.5 branch 2 times, most recently from e7f5b16 to d60553e Compare November 9, 2022 18:00
@disassembler disassembler force-pushed the coot/cardano-node-1.35.5 branch from d60553e to 8e3b963 Compare November 9, 2022 18:13
@coot
Copy link
Contributor Author

coot commented Nov 9, 2022

bors merge

@iohk-bors
Copy link
Contributor

iohk-bors bot commented Nov 9, 2022

@iohk-bors iohk-bors bot merged commit e933084 into release/cardano-node-1.35.x Nov 9, 2022
@iohk-bors iohk-bors bot deleted the coot/cardano-node-1.35.5 branch November 9, 2022 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants