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

Subgraph instance failed to run: Failed to process trigger in block XXXX #2353

Closed
AlexBHarley opened this issue Apr 7, 2021 · 5 comments · Fixed by #2670
Closed

Subgraph instance failed to run: Failed to process trigger in block XXXX #2353

AlexBHarley opened this issue Apr 7, 2021 · 5 comments · Fixed by #2670
Assignees

Comments

@AlexBHarley
Copy link

Do you want to request a feature or report a bug? Report a bug

What is the current behavior? The sub graph stalls at around 1% with the error Subgraph instance failed to run: Failed to process trigger in block #190080 (ac57ac5a96108b0f133ac6bac59e1bd0df0263d248a4fcc36393464b7c73835d), transaction ac57ac5a96108b0f133ac6bac59e1bd0df0263d248a4fcc36393464b7c73835d: Found no transaction for event, code: SubgraphSyncingFailure, id: QmfBAFQ6JX1QyVG8rfzUYSkax6Lot4j7qaTWdGVZcYWEsL.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

Here's the link to my Discord message, but concretely here is my bash history.

10020  graph init --from-contract 0x471EcE3750Da237f93B8E339c536989b8978a438 --network celo --abi ../celo-monorepo/packages/protocol/build/contracts/GoldToken.json alexbharley/celo-token ./celo-token
10021  cd celo-token
10023  yarn
10024  yarn codegen
10022  yarn deploy
10025  graph auth https://api.thegraph.com/deploy/ XXX
10026  yarn deploy

Here is:

What is the expected behavior? The subgraph builds without error and I can query it.

@leoyvens leoyvens self-assigned this Apr 7, 2021
@azf20
Copy link
Contributor

azf20 commented May 28, 2021

There appear to be no transactions in the error block on Celo: https://explorer.celo.org/blocks/190080/transactions

@azf20
Copy link
Contributor

azf20 commented Jul 8, 2021

This appears to relate to Epoch rewards on Celo. These appear in eth_getLogs but do not have a corresponding transaction. Investigating with the Celo team.

@azf20
Copy link
Contributor

azf20 commented Jul 8, 2021

This has also affected this subgraph

@azf20
Copy link
Contributor

azf20 commented Jul 9, 2021

This likely requires an update to the Celo client so that a transaction is returned for eth_getTransactionByHash for these epoch logs

@leoyvens
Copy link
Collaborator

@AlexBHarley This is issue happens when the subgraph tries to process an epoch reward event from Celo. Does your subgraph need those events, or would you be happy if the subgraph just skipped over those?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants