-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
eth_getLogs returns empty array in v2.34.0 #6598
Comments
Same issue on my side. Rollback to 2.33.1 resolved the issue |
Have experienced this as well. What's weird is that it sometimes works - but most of the time it does not work and just returns an empty array. Tested and experienced this on Ethereum. Before anyone asks, you get the same result regardless if you wrap your topics or not ( |
Thanks for reporting. Reproduced |
Oh, I did not realise it is for polygon, so I cannot reproduce for now, will need to try to reproduce on Ethereum |
@AlexeyAkhunov this seems to be a problem regardless of chain (both Ethereum and Polygon) - will reproducing on both chains need to be necessary? Another detail: it seems like the few times eth_getLogs actually does return data, it varies how many logs it actually manages to return for the same block across multiple requests. |
I don't have a working Polygon node, therefore I cannot reproduce in Polygon, but I think I might be able to reproduce on Ethereum Mainnet, but I am not sure yet |
I think I have reproduced, will investigate further tomorrow |
Ok, I found what caused this |
I have made a tag for the patch release, v2.35.1, could you please try. Will publish tomorrow after some more testing |
@AlexeyAkhunov unfortunately it does not appear to have fully resolved it for us. We're doing a repeating curl, and this is the number of bytes in each response (we'd expect this to be constant since we're querying a specific block number):
(42 bytes means that it returned an empty array) Edit: It does potentially seem like it's returning data more often than returning empty compared to before, but it still seems flakey as I'd expect it to return data, and the same amount of data, on each query. |
@boxhock thank you. I only fixed what I could reproduce. So which query are you using? I still don't have Polygon node, so I cannot reproduce that one. Also, is the version 2.33.1 definitely free from this defect? |
@AlexeyAkhunov, I work with @boxhock We cannot confirm it specifically didn't occur on eth with 2.33.1 as our nodes never ran that version. We observed it first on 2.34.0. Example against our Ethereum archive node running Erigon 2.35.1: Immediately running the same curl again: This is noticeable across all chains, including ethereum. |
@drcliche thank you! Can you try this on |
@AlexeyAkhunov Apologies for the lag and thank you for looking into this. Now running
|
@drcliche, @boxhock - I've just run that curl and got nothing back, my node is behind the tip by a long way and syncing though but has that block.... it looks like you're using bad params in your request. blockFrom should be fromBlock and likewise blockTo should be toBlock. When these are passed incorrectly the logs are read from the most recently executed block which is possibly why you're seeing an issue here. Could you try |
@hexoscott That does appear to work a lot more reliably on our synced nodes... I'll get with the team and see if that was just something that got kicked around backwards in testing or if that was actually the issue all along. |
@drcliche - great thanks, let me know either way if you could :) hopefully it was just a simple typo |
Going to close this down, if the issue is still there feel free to re-open and we'll pick the thread back up. |
Thanks @hexoscott ! We have verified things are good now. It looks like the reversion at 2.34.0 was the issue, then a bad test case was used from there. |
Great! Thank you for confirming! |
@hexoscott Can you please look at this same issue with bsc-erigon? |
System information
Erigon version: v2.34.0
OS & Version: Linux
body:
In 2.33.1, the result is normal, but in 2.34.0, an empty array is returned.
The text was updated successfully, but these errors were encountered: