coot issues

Results 240 issues of


                                            coot

trafficstars

Block fetch should keep in-flight limit in terms of bytes

block-fetch

Document our design on timeouts

This is important for reviewers to understand the implementation. See #1575.

documentation

R9B

NTP client: use io-sim-classes

This way we will gain access to cross platform `timeout` function which can be used to timeout requests.

ntp-client

Idle state timeouts for multi-chunk messages

For protocol states where there is no timeout (e.g. idle states) we should implement timeouts for receiving multi-chunk messages. Most of the messages in idle state are small with exception...

block-fetch

tx-submission

Avoid `binary` in MuxSDU encoding.

We can write directly to a memory location similar to what the `Storable` class does.

optimisation

mux

Add pipelined chain-sync client to `demo-chain-sync`

testing

optimisation

chain-sync

Test pipelined clients over a channel

* [ ] `req-resp` mini-protocol * [ ] `block-fetch` mini-protocol * ~[ ] `tx-submission` mini-protocol~ * [x] `chain-sync` mini-protocol

testing

block-fetch

Handshake client / server and direct

The handshake protocol does not have `GADTs` presentations, and no `direct` function is defined. These should be quite simple to implement and add.

testing

technical debt

handshake

Add tests for `codecChainSyncId`

testing

chain-sync

Use PingPong stateful pipelined clients to enhance stateful driver tests

* [x] Added `Network.TypedProtocols.Stateful.PingPong.Client` clients * [ ] Add `Network.TypedProtocols.Stateful.PingPong.Examples` example clients * [ ] Add tests in `Test.Ouroboros.Network.Driver`

testing

typed-protocols

local-state-query