- We finished high and low level peer sharing design. See Peer Sharing Implementation Plan
- We started working on low-level design of eclipse evasion (work in progress).
- We decided to use peer sharing instead of overloaded and ambiguous gossip term. PR input-output-hk/ouroboros-network#3980
- We fixed technical dept issue input-output-hk/cardano-node#3905 in the simulation testing of diffusion PR input-output-hk/cardano-node#4004
- We deployed all our nodes using our new nix based deployment architecture.
When deploying we found an issue in the
- Recently we found out that the consensus does not log exceptions thrown during
intiialisation. This was fixed in
As part of this pull request we also changed that all exceptions rethrown by
the connection handler thread are wrapped in
Some older items, which were not announced
- We identified and fixed an issue related to socket activation (socket options
where not set for sockets passed through socket activation).
This fix will be released in the next
- We extended the NixOs service module so that one can modify
stateDiroptions. PR input-output-hk/cardano-node#4196
We resolved a number of issues before release of
io-sim on hackage:
- issue input-output-hk/ouroboros-network#2797
- issue input-output-hk/ouroboros-network#2650
- issue input-output-hk/ouroboros-network#3436
- issue input-output-hk/ouroboros-network#2588
- issue input-output-hk/ouroboros-network#2587
- issue input-output-hk/ouroboros-network#2586
See PR #24.
We also improved experience for contributors of
typed-protocols by adding issue templates:
- We pushed a branch which identifies a GHC quirk: coot/typed-protocols-rewrite-StateToken-problem. That's too be resolved in order to push forward review of the redesign in PR input-output-hk/typed-protocols#3.
- As for
io-sim, we wrote issue templates: PR input-output-hk/typed-protocols#11
Input Endorsers Simulation
New features include:
Histograms of block arrival frequency, for both network (inbound) and CPU (block validation). This is interesting to check that we're not overloading the CPU block validation capacity, or network link capacity. Or alternatively to observe the behaviour in an overload situation if we set the block generation rate high enough.
Pie chart of utilisation of TCP links. This shows how small a fraction of links are being used at any one time, and shows that once the system "warms up" and is operating stably, most block delivery is ballistic.
Showing off the new screen layout combinators, that let us put multiple charts, titles etc on screen at once and scale them to whatever screen or video resolution we like without having to tweak numbers (this example is scaled to fit 1080HD video resolution).