coot

To address this we need to extend [`ExpandedInitiatorContext`](https://ouroboros-network.cardano.intersectmbo.org/ouroboros-network-framework/Ouroboros-Network-Context.html#t:ExpandedInitiatorContext) which is used by `node-to-node` clients.

I realised that Consensus might actually be interested in a signal from the outbound governor which summarises all connections. If we just expose `IsLocalRoot` in `ExpandedInitiatorContext` then on the consensus...

I used wrong name, it's about counters not targets.

We found out that the memory leak was resolved when the number of pipelined messages was reduced to a small number. There's more information about it in an unfortunately private...

We implemented a way to use duplex connections in IOG, although in a more complex scenario. We have a component which tracks state of the connection, e.g. in which direction...

I haven't used atp for a very long time (it's just to heavy for my current latex work), and I stopped maintaining it due to time constraints; I encourage you...

We have 15 jobs each is caching between 50MB to 100MB, so it does not exceed the the 10GB cache limit.

Thanks @chase this indeed made it work. There's certainly something wrong, since we only use Windows machines in GitHub Actions.

Because this was fixed in `9.2` and we are already building the `cardano-node` with `ghc-9.2` I think this can be closed.

> We've added the following patch: https://github.com/input-output-hk/ouroboros-network/pull/1423/files#diff-b6eac6cb1f63c584aee3e94132101030, and I believe we should do the following: You probably wanted to point [here directly](https://github.com/input-output-hk/ouroboros-network/pull/1423/commits/5bcdd7a735807f0064ea1b0706c660b1cc96f802).