Chris Wessels
Chris Wessels
Feel free to submit a PR @anthonyboutinov
+1 for this issue. Can I provide any details that may help?
+1. The example should include minimal dependencies, so I'd go with NeDB. It sucks having to strip out Mongo.
Worth noting that there are risks here. If the default pattern becomes for indexers to download existing state, then we have far less actors actively validating that state's integrity and...
This is how the `indexer` components work. `indexer-agent` exposes an indexer management GraphQL API, and `indexer-cli` presents a CLI interface over this strongly typed and inspectable API.
In both instances, there's a client and a server. In both instances, the connection between them must be secured. Today the client is `graphman` and the server is PostgreSQL. With...
I've observed these myself: (Same as OP) On block `13380098` (`38d484acc0f3fe698ac05340877f5d8f766bb23f03883797a6e8452fb524b3aa`) subgraph `QmWXF3jTLo6Wy9MxDZz6WKhET3GFcSFqn6vmrDDYPF7UHK` failed with ``` failed to process trigger: block #13380099 (0x38d4…b3aa), transaction ca32b1581b837c6ca539cf6c2fd542e9bcacbdc345c6a424382b4f0e48b96153: function handleSwapped not found ```...
Another failure that should be deterministic: On block `14043344` (`5662c33b8e598339ced77eeb6bf4e58061528192bbaf907b309cc7fd6bfebee5`) subgraph `QmRA6mjFXCmzYp5MwHzyHpUVehG6zNuL9xCw6oj4VD9HyZ` failed with ``` failed to process trigger: block #14043345 (0x5662…bee5), transaction 4499dc75facb4cd27894196aac00bcb0ffbe3d64de87105878451d5637662f90: Generating function inputs for the call...
Looks like the `Generating function inputs for the call failed` variant has been fixed in the 0.25.1 release: https://github.com/graphprotocol/graph-node/issues/3194