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
[Bug] eth_call constantly reverting when called from the mapping handler #5035
Comments
hey @itsjerryokolo are you calling the Polygon RPC at the specific block height? Can you share the logs & the RPC call you're making? |
@azf20 No, I didn't, but I tried it yesterday and got response. This is the handler
It fires in this event |
Thanks - can you share how you're calling with ethers.js? |
Full Code
|
I can confirm that calling the function at the block returns a result as expected.
@incrypto32 any idea what might be happening here which would prevent this call from returning as expected in the subgraph? Maybe something to do with the underscores? |
@azf20 i'll investigate. |
Hi guys, we managed to fix the deployment issue, we don't know the cause but seems to be related to the graph-cli version, we updated it to version 0.62.0 and the deployment went through. The issue was only on polygon, other chains didn't had the issue. Thanks @itsjerryokolo for reporting it |
Closing this issue as it was related to the RPC provider and not graph-node itself. |
Bug report
Calling the
_badgeStore()
function is constantly reverting. I tried calling the same function through our polygon RPC using etherjs and I got response.Steps to reproduce:
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
OS information
None
The text was updated successfully, but these errors were encountered: