-
Notifications
You must be signed in to change notification settings - Fork 943
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
Mainnet subgraph failed, with required capabilities: : A matching Ethereum network with NodeCapabilities { archive: false, traces: false } was not found. #3915
Comments
Additional info, if I delete the following event handler, the error is gone:
|
Hi! Are you still having the above issue? I think there might have been a temporary glitch with the mainnet provider around a deployment |
I just got this issue as well, not sure why. Any ideas around this? I feel this could be an RPC issue. |
Hi - what network are you indexing and where are you deploying? |
I am facing the same issue but with the Mumbai network because of callHandlers in my case. |
For mainnet, I think this is an instance of #3204 |
Can you explain what you mean by that? |
@pheuberger certain subgraph features (e.g. callHandlers) rely on the optional |
A bug.
I try to deploy a subgraph to Mainnet mpmain and face this error:
Failed to start subgraph, code: SubgraphStartFailure, error: expected triggers adapter that matches deployment QmV4H49cp81n36EcHcEgKn1AMaie2LoTxu2vs1fm6UXRus[396313] with required capabilities: : A matching Ethereum network with NodeCapabilities { archive: false, traces: false } was not found.
When I deploy this subgraph to Rinkeby metapoker everything works fine.
The text was updated successfully, but these errors were encountered: