Skip to content
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

[Failed-Request-Alert-Tuning] Investigate and resolve the bug causing the Received an invalid integer type: null error in EthImpl.getBlock() function #3346

Closed
quiet-node opened this issue Dec 20, 2024 · 1 comment · Fixed by #3349
Assignees
Labels
bug Something isn't working

Comments

@quiet-node
Copy link
Member

quiet-node commented Dec 20, 2024

Description:

Approximately 60,000 results on mainnet have been logged with the error Received an invalid integer type: null, with no additional diagnostic details provided. This issue is a significant contributor to 500 errors for eth_getBlockByHash and eth_getBlockByNumber. The problem lied in the EthImpl.getBlock() which is shared by both of the endpoint. The closest trace log states, Synthetic transaction hashes will be populated in the block response, suggesting the issue occurs after the populateSyntheticTransactions() process. The root cause likely resides in the ReceiptsRootUtils.buildReceiptRootHashes() method or during the creation of a new Block().

Solution:

Investigate and resolve the bug causing the Received an invalid integer type: null error in EthImpl.getBlock() function

@quiet-node
Copy link
Member Author

clsoing as duplicated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant