Viacheslav
- [x] https://github.com/celestiaorg/celestia-node/pull/1038 - [x] https://github.com/celestiaorg/celestia-node/pull/1046 - [x] https://github.com/celestiaorg/celestia-node/pull/1135 - [x] https://github.com/celestiaorg/celestia-node/pull/1153
start syncing was rework in https://github.com/celestiaorg/celestia-node/pull/917/commits/2c232ee7dff3d5b4461da21f13b0bfeaf500e8e5 It was added as a separate commit in order to show the difference between two approaches. @Wondertan , please take a look at diff.
TestBlockFetcherHeaderValues failed due to race in celestia-core: ``` WARNING: DATA RACE Write at 0x0000020a3cf0 by goroutine 111: github.com/tendermint/tendermint/rpc/core.SetEnvironment() /home/runner/go/pkg/mod/github.com/celestiaorg/[email protected]/rpc/core/env.go:44 +0xa18 ```
https://github.com/celestiaorg/celestia-node/issues/1032
> why was this resolved? What is this error check even doing? It was left by mistake after resolving all merge conflicts. Will remove it
> Your case likely happened because of reconnects that might be a symptom of another issue Yes, peer.Id can be received from this channel only once. If it appears one...
No. Fraud sync does not affect full reconstruction test.
https://github.com/celestiaorg/celestia-node/issues/1058
https://github.com/celestiaorg/celestia-node/issues/1007