Vlad
Vlad
### Implementation ideas Unit test is flaky with and occasionally fails with error: ``` Received unexpected error: deliverTxSub was cancelled (reason: CometBFT exited) ```
Add telemetry for server side of bitswap (blockstore) operations.
### Implementation ideas Shrex server implementation should know in advance the amount of data expected to be read from the stream. Use io.LimitReader on server side.
### Implementation ideas Blobstream API is missing in https://node-rpc-docs.celestia.org/?version=v0.17.1
### Implementation ideas Add runtime / system level metric to have observability of disk iops
### Implementation ideas Add API to sign an arbitrary bytes using node key and return it to the caller.
### Implementation ideas Currently, celestia-node requires a single core.Ip for posting data. If that IP is unavailable, the node can't post data, leading to failure. Suggestion: Allow users to specify...
Refactor the action to: - compare changes with target branch instead of main - detect base branch changes to trigger ci - don't apply kind:break! if breaking changes are detected,...
### Implementation ideas Need to add system resources consumption metrics: - disk space used: - headers - blocks data - Bandwidth
Instead of running prometheus server, send prometheus collected metrics by otel exporter