Nguyen Nhu Viet
Nguyen Nhu Viet
Just for reference: We need to keep an eye on these 2 PRs (sdk/app) - https://github.com/celestiaorg/cosmos-sdk/pull/243 - https://github.com/celestiaorg/celestia-app/pull/472
Revisit on the next grooming session after #483 is done Now we can get stuck in rebase issues if done in parallel
Ref: https://github.com/celestiaorg/celestia-node/issues/895
Grooming 12/07/2022: Changing the issue from Post-Mainnet to Mainnet - it's still a low priority one - we can defer it again to Post-Mainnet if we don't have the capacity
The root cause is lying in data not available and we will keep this issue opened as the reference for future issues with the same root causes This should be...
Grooming 12/07/2022: 1. Moving to Post-Mainnet 2. Extraction should be done after #878
Same error msg as here: https://github.com/celestiaorg/celestia-node/issues/759
Added #709 after grooming
same happens in swamp tests Ref: https://github.com/celestiaorg/celestia-node/issues/955
We should revisit https://github.com/celestiaorg/celestia-node/issues/504 and close it if after implementation of parallelisation, the issue is not reproducible again