[X] This is not a security-related bug/issue. If it is, please follow please follow the security policy.
[X] I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
[X] I am running the Latest release, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
[X] I did not make any code changes to lotus.
Lotus component
[ ] lotus daemon - chain sync
[ ] lotus fvm/fevm - Lotus FVM and FEVM interactions
[ ] lotus miner/worker - sealing
[ ] lotus miner - proving(WindowPoSt/WinningPoSt)
[X] lotus JSON-RPC API
[ ] lotus message management (mpool)
[ ] Other
Lotus Version
All recent versions ( 1.29.1, master, etc )
Repro Steps
Run lotus chain export --recent-stateroots 1802 --skip-old-msgs /dev/null (done with calibnet for expedience)
Checklist
Latest release
, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Repro Steps
Run
lotus chain export --recent-stateroots 1802 --skip-old-msgs /dev/null
(done withcalibnet
for expedience)/dev/null
guarantees non-blocking instantaneous writes.When the export is half-way done, observe tons of messages from the
cli
(not daemon) side:Describe the Bug
Current default settings of the jsonrpc emitter seem incompatible with chain exporting mode.
Logging Information