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

[Bug] handle reverted eth_calls on declared eth_calls #5514

Open
1 of 3 tasks
Shiyasmohd opened this issue Jun 27, 2024 · 0 comments
Open
1 of 3 tasks

[Bug] handle reverted eth_calls on declared eth_calls #5514

Shiyasmohd opened this issue Jun 27, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Shiyasmohd
Copy link

Bug report

Declared eth_calls executes before eth_calls on handlers triggered. But when declared eth_calls get reverted, subgraph get stuck in syncing.

Repo that can reproduce this error - Link
Deployment ID: QmfH5xCioLUqd1zM2b2QGE6Br5uZdks2tx2A1NPB1dZQSK

Subgraph that sync when declared eth_call is removed
Deployment ID: QmaWD3fz3Y6PZdEmZ9QQ79fkVwTzh49JBqLcbzG85wDMrr

Relevant log output

Error: Ethereum node returned an error for an eth_call: RPC error: Error { code: ServerError(-32015), message: "VM execution error.", data: Some(String("Reverted ERC721URIStorage: URI query for nonexistent token")) }

IPFS hash

QmfH5xCioLUqd1zM2b2QGE6Br5uZdks2tx2A1NPB1dZQSK

Subgraph name or link to explorer

No response

Some information to help us out

  • Tick this box if this bug is caused by a regression found in the latest release.
  • Tick this box if this bug is specific to the hosted service.
  • I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

@Shiyasmohd Shiyasmohd added the bug Something isn't working label Jun 27, 2024
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
Development

No branches or pull requests

1 participant