-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lack of transaction receipts (eth_getTransactionReceipt) for some of FEVM transactions #11325
Comments
FWIW our archive appears to have, at least some of, the missing tx receipts Query:
Response:
Query:
Response: Query:
Response:
|
My first concern is that, while we do backfill the index if the "txhash" database doesn't exist, that logic may not be race-free. However, the range is so large this seems unlikely. Did you enable the Eth JSON-RPC API after syncing that range? In that case, you could be missing the events (which will, apparently, cause the lotus API to return "nothing" instead of an error in this case). |
All these cases here are actually errors and returning `nil` makes this hard to debug. We likely returned nil in the past to be "best effort" but, as far as I can tell, we should only hit these error cases if something is actually wrong. part of #11325
We were using node set up by other company. This is the answer I've got from them
Also I'd like to add that after initial indexing process when we have found missing receipts we've made a check to investigate the scale of problem and after this check we have found that some of receipts were available - it seems that their availability has changed over time, so maybe they were indexed by the node until the code that was supposed to investigate the scale of the problem was run. |
So, I think the issue is:
Those events would be re-created if/when you re-execute a tipset (e.g., ask for an execution trace) which would explain why they're re-appearing. The solution would be to re-execute all of those tipsets (possibly in parallel). If your upstream provider is willing to apply a patch, #11329 will give us actual error messages instead of just returning "nil" for missing receipts. |
So, there's actually a decent solution: re-execute tipsets on-demand to fill in missing event information. We usually like to avoid this kind of thing for performance reasons however:
|
At the moment we've received access to other Lotus archive instance without described issues within task. The node instance with missing receipts errors was probably discarded. |
All these cases here are actually errors and returning `nil` makes this hard to debug. We likely returned nil in the past to be "best effort" but, as far as I can tell, we should only hit these error cases if something is actually wrong. part of #11325
I'd like to keep this open for now as it's still an issue and still something I'd like to eventually address. |
All these cases here are actually errors and returning `nil` makes this hard to debug. We likely returned nil in the past to be "best effort" but, as far as I can tell, we should only hit these error cases if something is actually wrong. part of #11325
Checklist
Lotus component
Lotus Version
Repro Steps
Request
Response
Describe the Bug
We are indexing Filecoin blocks using Lotus node. We have found that for transactions in FEVM we did not get transaction receipts.
Today, we have indexed data from blocks in range from 2_683_348 to 2_846_394 searching of transactions with missing receipt.
In this range we found 53_082 transactions without receipt in 11_068 blocks.
First block with transaction which has not receipt on node: 2_683_360
Last block with transaction which has not receipt on node: 2_792_027
Is it a node issue or something we don't see?
Samples
Transactions which have not receipt on node:
2683360,0x197bb7dc4af0fa587b913827f6c626d695a5205427656e26f7637fba03f88325,bafy2bzacebctgcd4fi5m23446hzhuel7mbxnotffkkufuqgpcwgbisduy3ujk
Explorer: https://filfox.info/en/message/0x197bb7dc4af0fa587b913827f6c626d695a5205427656e26f7637fba03f88325?t=3
Node:
2683375,0x67e59d73c92fa1c0cfc666038fc52a7264135d9d5b66434a77fcef548c383113,bafy2bzaceblwl7zvemx5ovsxhryjdjb4npnlyilmwtktj77qp22ni2atccqvo
Explorer: https://filfox.info/en/message/0x67e59d73c92fa1c0cfc666038fc52a7264135d9d5b66434a77fcef548c383113?t=3
Node:
2683381,0x03cf7eaf8a370974988affde7ee4527c379c3cb4b60af552064995e6a4890d05,bafy2bzacec7247sycph26tnoaqnvo62no4pmtkosmedbnl2d3m5ucdzsnk22u
Explorer: https://filfox.info/en/message/0x03cf7eaf8a370974988affde7ee4527c379c3cb4b60af552064995e6a4890d05?t=3
Node:
Transactions which have receipt on node
2683363,0x3a59331d838a4c0da768bc0ec02904aa6e19f9fd6748ce60c1bec649919a4573,bafy2bzaceamyzkhzoe4v3esemhyzuaqv2tllne3dyf7kwsrnmwvh77y7kunri
Explorer: https://filfox.info/en/message/0x3a59331d838a4c0da768bc0ec02904aa6e19f9fd6748ce60c1bec649919a4573?t=3
Node:
2683365,0xaaae15af843cda1981f33fea3d4b7dfd97abef277d94ceaf16a49af360d99830,bafy2bzacedzxyboeysnc552mboimvqraeipeqeibmgrkldfgpvp3ldzuzvz56
Explorer: https://filfox.info/en/message/0xaaae15af843cda1981f33fea3d4b7dfd97abef277d94ceaf16a49af360d99830?t=3
Node:
Tooling
Configuration Options
The text was updated successfully, but these errors were encountered: