[X] This is not a security-related bug/issue. If it is, please follow please follow the security policy.
[X] This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
[X] This is not a new feature request. If it is, please file a feature request instead.
[X] This is not an enhancement request. If it is, please file a improvement suggestion instead.
[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, or 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
[X] lotus daemon - chain sync
[ ] lotus miner - mining and block production
[ ] lotus miner/worker - sealing
[ ] lotus miner - proving(WindowPoSt)
[ ] lotus miner/market - storage deal
[ ] lotus miner/market - retrieval deal
[ ] lotus miner/market - data transfer
[ ] lotus client
[ ] lotus JSON-RPC API
[ ] lotus message management (mpool)
[ ] Other
Lotus Version
idk
Describe the Bug
Thanks to @ribasushi we have some evidence of compaction erroring on startup because receipts are not added to snapshot. It appears that this happens in messages mode but maybe discard mode (need to examine config below)
This is a bug which we can fix. However this problem resolves itself after ~4 finalities when the receipts are computed. So its probably not the root cause of discard not discarding.
Im starting to suspect that this is an issue with not entering warmup properly since I think this is exactly the point of warmup. Will need to dig further.
Checklist
Latest release
, or 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
Describe the Bug
Thanks to @ribasushi we have some evidence of compaction erroring on startup because receipts are not added to snapshot. It appears that this happens in messages mode but maybe discard mode (need to examine config below)
This is a bug which we can fix. However this problem resolves itself after ~4 finalities when the receipts are computed. So its probably not the root cause of discard not discarding.
Logging Information
node configured: