coot
coot
Take a decision if we want to remove [Test.Ouroboros.Network.MockNode](https://github.com/input-output-hk/ouroboros-network/blob/master/ouroboros-network/test/Test/Ouroboros/Network/MockNode.hs) module. By now`ouroboros-consensus` has a well designed testing architecture, and we can focus on network level tests only.
https://docs.microsoft.com/en-us/windows/win32/ipc/pipe-names
We can use [WriteFileGather](https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-writefilegather) to write lazy bytestring into `HANDLE`s - for both files and named pipes.
To support https://github.com/input-output-hk/cardano-node/issues/1875
Like the network magic is included. This will avoid using `Byron` or `Shelley` when one really needs to run hardfork combinator. This will be useful in 6-8 weeks when integrating...
Currently the flow of data in `cardano-node` is not very clear. Partially the confusion comes from the fact that `runDataDiffusion` is run by consensus application. The current flow is: _environment_...
There are two servers there: pipelined and non pipeliend, the pipelined one should go into `Ouroboros.Network.Protocol.TxSubmission.PipelinedServer` (as in other mini-protocols, the pipelined peers are in a separate module).
We recently found that #2052 went through CI without being noticed. We need to review our integration tests.
Implement a high performance file server which reads ranges from files and sends them over the network - mimicking the architecture of `ouroboros-consensus` storage layer, but not using it. This...