dustinxie

the current json output is for purpose of ELK processing, if we want a better console output, need to make sure does not break ELK functionality (like still outpu json...

create 1 PR for moving each struct, like Consensus struct {}, BlockSync struct {}

put this on a brief hold, #3511 should solve the import cycle, try again after 3511 merges

> put this on a brief hold, #3511 should solve the import cycle, try again after 3511 merges 3511 has merged, pls try again

@saitofun wait #3401 to merge first before start working on this one

here's the tx that cannot pass fullsync: https://testnet.iotexscout.io/tx/40fe566ea234d7db531aca486196ade1f7eb81c0b185b80c7dd238f1401bb95d 1. the culprit is identified to be: https://github.com/ethereum/go-ethereum/commit/9393d1fb5d178667e4d2750f7f540a3db5985818 2. after this commit, the consumed gas changed from `2907839` to `2892839` 3. continue...

how to repro 1. good code: iotex-core/fuzzer branch (using go-ethereum/fuzzer branch) 2. bad code: iotex-core/arrow branch (using go-ethereum/arrow branch == fuzzer branch + culprit commit mentioned above) 3. data file:...

[good.log](https://github.com/iotexproject/iotex-core/files/9456144/good.log) [bad.log](https://github.com/iotexproject/iotex-core/files/9456148/bad.log)

see comment in https://github.com/iotexproject/iotex-core/issues/3476, we need to achieve: 1. the output to log file is still same json format, for ELK log collection/analysis purpose 2. on top of that, if...

@ligi can you check the PR again? we set up the chain explorer, https://nightly.iotexscan.io/ is up and running now