Open elmattic opened 1 month ago
This issue exists because the snapshots don't contain receipts, nor, therefore, event data. If you did this and requested later than 2023775
it should be fine. But requesting 0x1ee13f
/ 2023743
is within the snapshot. With https://github.com/filecoin-project/lotus/pull/12655 it'll be easier to backfill after importing a snapshot but still not something we're enabling by default because it's quite expensive since the tipsets all need to be re-executed again to get their data.
The thing that does concern me about this is the fact that it doesn't return an error. I'd like the resolution to this issue to be that we error when we haven't indexed that tipset. But it could be that https://github.com/filecoin-project/lotus/pull/12655 already does that, we should test and confirm and fix if not.
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
LOTUS_FEVM_ENABLEETHRPC=1 ./lotus daemon
{"id":1,"jsonrpc":"2.0","result":[]}
Describe the Bug
According to Filecoin explorers (filfox or filutils), we should obtain five logs for this block number:
https://calibration.filutils.com/en/message/0xb3d54c1a06a9b6f6e752d5621a086f140d7e322512e05a270fccb439c47cf9da https://calibration.filutils.com/en/message/0xb17fc66619ba84c74d0b0c7be8e8acf56ffaa9248845730ade6ee16f10d9cd1c
Note that for some epochs, I do see logs, but for some, I don't see them and have an empty list as a result.
Logging Information